summaryrefslogtreecommitdiff
path: root/drivers/input/mouse
diff options
context:
space:
mode:
authorDmitry Artamonow <mad_soft@inbox.ru>2012-04-12 15:33:34 +0400
committerSamuel Ortiz <sameo@linux.intel.com>2012-04-16 20:57:26 +0400
commit02269ab10f1130d35dc35db72ab026d16ba31abf (patch)
treeeb6663b963cf6e5fd127ae19e6fb0e611780080e /drivers/input/mouse
parent1fcb57d0f6e1150003d222051aaaf4bc4a9ccc94 (diff)
downloadlinux-02269ab10f1130d35dc35db72ab026d16ba31abf.tar.xz
mfd: Fix asic3_gpio_to_irq
Assumption that irq numbers of asic3 gpios start at IRQ_BOARD_START is certainly wrong - driver may as well use any other base for its irqs (consider for example the imaginary case of two ASIC3 chips onboard) Furthermore, some platforms even don't have IRQ_BOARD_START defined, so driver will fail to build on them: ------------------------------------------------------- drivers/mfd/asic3.c: In function 'asic3_gpio_to_irq': drivers/mfd/asic3.c:530: error: 'IRQ_BOARD_START' undeclared (first use in this function) drivers/mfd/asic3.c:530: error: (Each undeclared identifier is reported only once drivers/mfd/asic3.c:530: error: for each function it appears in.) ------------------------------------------------------- Fix it by using irq_base from driver data. Signed-off-by: Dmitry Artamonow <mad_soft@inbox.ru> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/input/mouse')
0 files changed, 0 insertions, 0 deletions