From: Randy Dunlap <rdunlap@infradead.org>
To: "Life is hard, and then you die" <ronald@innovation.ch>,
YueHaibing <yuehaibing@huawei.com>
Cc: dmitry.torokhov@gmail.com, hsweeten@visionengravers.com,
robh@kernel.org, arnd@arndb.de,
andriy.shevchenko@linux.intel.com, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: applespi: Fix build error without CONFIG_PCI
Date: Thu, 18 Jul 2019 21:05:47 -0700 [thread overview]
Message-ID: <6a7111e2-3347-11fa-58d9-11d337a91c42@infradead.org> (raw)
In-Reply-To: <20190718114036.GA2872@innovation.ch>
On 7/18/19 4:40 AM, Life is hard, and then you die wrote:
>
> On Thu, Jul 18, 2019 at 10:06:54AM +0800, YueHaibing wrote:
>> If CONFIG_KEYBOARD_APPLESPI is set to y, but
>> CONFIG_PCI is not set, building will fails:
>>
>> drivers/spi/spi-pxa2xx-pci.c: In function pxa2xx_spi_pci_probe:
>> drivers/spi/spi-pxa2xx-pci.c:208:8: error: implicit declaration of function pcim_enable_device;
>> did you mean pci_enable_device? [-Werror=implicit-function-declaration]
>> ret = pcim_enable_device(dev);
>> ^~~~~~~~~~~~~~~~~~
>> pci_enable_device
>> drivers/spi/spi-pxa2xx-pci.c:239:8: error: implicit declaration of function pci_alloc_irq_vectors;
>> did you mean pci_alloc_consistent? [-Werror=implicit-function-declaration]
>> ret = pci_alloc_irq_vectors(dev, 1, 1, PCI_IRQ_ALL_TYPES);
>> ^~~~~~~~~~~~~~~~~~~~~
>>
>> Make CONFIG_KEYBOARD_APPLESPI depends on CONFIG_PCI
>> to fix this.
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Fixes: b426ac045209 ("Input: add Apple SPI keyboard and trackpad driver")
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>> ---
>> drivers/input/keyboard/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/input/keyboard/Kconfig b/drivers/input/keyboard/Kconfig
>> index dd934c4..fefcc46 100644
>> --- a/drivers/input/keyboard/Kconfig
>> +++ b/drivers/input/keyboard/Kconfig
>> @@ -74,7 +74,7 @@ config ATARI_KBD_CORE
>> config KEYBOARD_APPLESPI
>> tristate "Apple SPI keyboard and trackpad"
>> depends on ACPI && EFI
>> - depends on SPI
>> + depends on SPI && PCI
>> depends on X86 || COMPILE_TEST
>> imply SPI_PXA2XX
>> imply SPI_PXA2XX_PCI
>> --
>> 2.7.4
>
> I think this is more properly fixed by Dmitry's suggestion of making
> SPI_PXA2XX_PCI depend on PCI, since it's that module, not applespi,
> that actually needs PCI - see
> https://www.spinics.net/lists/linux-input/msg62351.html
Dmitry's patch works for my failing test case.
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Thanks.
--
~Randy
next prev parent reply other threads:[~2019-07-19 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 2:06 [PATCH] Input: applespi: Fix build error without CONFIG_PCI YueHaibing
2019-07-18 11:40 ` Life is hard, and then you die
2019-07-18 11:56 ` Arnd Bergmann
2019-07-19 4:05 ` Randy Dunlap [this message]
[not found] ` <CAK8P3a2H0o+_3Y_J3r=D5_hGCArTYeHPfPPjY3dJ+ArmqYrOfQ@mail.gmail.com>
2019-07-18 11:58 ` Life is hard, and then you die
2019-07-18 12:34 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a7111e2-3347-11fa-58d9-11d337a91c42@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ronald@innovation.ch \
--cc=yuehaibing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).