From: Linus Walleij <linus.walleij@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
kbuild-all@lists.01.org, linux-gpio@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [linusw-pinctrl:devel 26/32] kismet: WARNING: unmet direct dependencies detected for PINCTRL_IMX when selected by PINCTRL_IMX8MM
Date: Mon, 5 Sep 2022 23:08:11 +0200 [thread overview]
Message-ID: <CACRpkdaLQ68VfYCfv40hGuGnpaMKchiTOSTJy9rnDKnBOQnFDw@mail.gmail.com> (raw)
In-Reply-To: <202209050952.vfkohsRg-lkp@intel.com>
On Mon, Sep 5, 2022 at 3:55 AM kernel test robot <lkp@intel.com> wrote:
> kismet warnings: (new ones prefixed by >>)
> >> kismet: WARNING: unmet direct dependencies detected for PINCTRL_IMX when selected by PINCTRL_IMX8MM
>
> WARNING: unmet direct dependencies detected for PINCTRL_IMX
> Depends on [n]: PINCTRL [=y] && OF [=n]
> Selected by [y]:
> - PINCTRL_IMX8MM [=y] && PINCTRL [=y] && SOC_IMX8M [=y]
I have a hard time to understand these warnings at times, but I suspect
you need a
depends on OF
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-09-05 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 1:54 [linusw-pinctrl:devel 26/32] kismet: WARNING: unmet direct dependencies detected for PINCTRL_IMX when selected by PINCTRL_IMX8MM kernel test robot
2022-09-05 21:08 ` Linus Walleij [this message]
2022-09-05 21:21 ` Francesco Dolcini
2022-09-06 11:46 ` Linus Walleij
2022-09-06 20:30 ` Francesco Dolcini
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 8:43 kernel test robot
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=CACRpkdaLQ68VfYCfv40hGuGnpaMKchiTOSTJy9rnDKnBOQnFDw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=fazilyildiran@gmail.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--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).