From: Sekhar Nori <nsekhar@ti.com>
To: Necip Fazil Yildiran <fazilyildiran@gmail.com>
Cc: geert+renesas@glider.be, arnd@arndb.de, paul@pgazz.com,
linux-kernel@vger.kernel.org, bgolaszewski@baylibre.com,
jeho@cs.utexas.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: davinci: fix kconfig dependency warning when !GPIOLIB
Date: Mon, 28 Sep 2020 23:43:08 +0530 [thread overview]
Message-ID: <a04c933d-9642-c211-1e49-7f564019d6ab@ti.com> (raw)
In-Reply-To: <20200914141954.337859-1-fazilyildiran@gmail.com>
On 14/09/20 7:49 PM, Necip Fazil Yildiran wrote:
> When MACH_DAVINCI_DA830_EVM is enabled and GPIOLIB is disabled, it results
> in the following Kbuild warning:
>
> WARNING: unmet direct dependencies detected for GPIO_PCF857X
> Depends on [n]: GPIOLIB [=n] && I2C [=y]
> Selected by [y]:
> - MACH_DAVINCI_DA830_EVM [=y] && ARCH_DAVINCI [=y] && ARCH_DAVINCI_DA830 [=y] && I2C [=y]
>
> The reason is that MACH_DAVINCI_DA830_EVM selects GPIO_PCF857X without
> depending on or selecting GPIOLIB while GPIO_PCF857X is subordinate to
> GPIOLIB.
>
> Honor the kconfig menu hierarchy to remove kconfig dependency warnings.
>
> Fixes: 77316f057526 ("davinci: DA830/OMAP-L137 EVM: use runtime detection for UI card")
> Signed-off-by: Necip Fazil Yildiran <fazilyildiran@gmail.com>
Here too, I think changing to "imply GPIO_PCF857X if I2C" is better.
Thanks,
Sekhar
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-28 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 14:19 [PATCH] ARM: davinci: fix kconfig dependency warning when !GPIOLIB Necip Fazil Yildiran
2020-09-28 18:13 ` Sekhar Nori [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=a04c933d-9642-c211-1e49-7f564019d6ab@ti.com \
--to=nsekhar@ti.com \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=fazilyildiran@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jeho@cs.utexas.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@pgazz.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).