From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Denis Turischev <denis@compulab.co.il>
Subject: Re: [PATCH -next v2] gpio: GPIO_SCH: depends on LPC_SCH
Date: Fri, 2 Apr 2021 21:20:06 +0300 [thread overview]
Message-ID: <YGdgVqf0QnWdjAjk@smile.fi.intel.com> (raw)
In-Reply-To: <20210402161751.7683-1-rdunlap@infradead.org>
On Fri, Apr 02, 2021 at 09:17:51AM -0700, Randy Dunlap wrote:
> Since LPC_SCH provides GPIO functionality, GPIO_SCH should depend on
> LPC_SCH to prevent kconfig warning and build errors:
>
> WARNING: unmet direct dependencies detected for LPC_SCH
> Depends on [n]: HAS_IOMEM [=y] && PCI [=n]
> Selected by [y]:
> - GPIO_SCH [=y] && GPIOLIB [=y] && X86 [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
>
> and
>
> ../drivers/mfd/lpc_sch.c:204:1: warning: data definition has no type or storage class
> module_pci_driver(lpc_sch_driver);
> ^~~~~~~~~~~~~~~~~
> ../drivers/mfd/lpc_sch.c:204:1: error: type defaults to ‘int’ in declaration of ‘module_pci_driver’ [-Werror=implicit-int]
> ../drivers/mfd/lpc_sch.c:204:1: warning: parameter names (without types) in function declaration
> ../drivers/mfd/lpc_sch.c:197:26: warning: ‘lpc_sch_driver’ defined but not used [-Wunused-variable]
> static struct pci_driver lpc_sch_driver = {
> ^~~~~~~~~~~~~~
Pushed to my review and testing queue, thanks!
> Fixes: 6c46215d6b62 ("gpio: sch: Hook into ACPI GPE handler to catch GPIO edge events")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
I have dropped these two since my SoB will be there. But also I think it's
better to narrow down this kind of Cc list as much as possible (for example, we
know that Bart and Linus are maintainers of GPIO, no need to include them
explicitly here, just use --cc parameter when sending).
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: linux-gpio@vger.kernel.org
> Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> Cc: Denis Turischev <denis@compulab.co.il>
> ---
> v2: change to "depends on LPC_SCH" as suggested by Andy
>
> drivers/gpio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20210401.orig/drivers/gpio/Kconfig
> +++ linux-next-20210401/drivers/gpio/Kconfig
> @@ -861,9 +861,9 @@ config GPIO_IT87
> config GPIO_SCH
> tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
> depends on (X86 || COMPILE_TEST) && ACPI
> + depends on LPC_SCH
> select GPIOLIB_IRQCHIP
> select MFD_CORE
> - select LPC_SCH
> help
> Say yes here to support GPIO interface on Intel Poulsbo SCH,
> Intel Tunnel Creek processor, Intel Centerton processor or
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-04-02 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 16:17 [PATCH -next v2] gpio: GPIO_SCH: depends on LPC_SCH Randy Dunlap
2021-04-02 16:38 ` Andy Shevchenko
2021-04-02 18:15 ` Andy Shevchenko
2021-04-02 18:20 ` Andy Shevchenko [this message]
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=YGdgVqf0QnWdjAjk@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=denis@compulab.co.il \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.