From: Linus Walleij <linus.walleij@linaro•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Hongzhou Yang <hongzhou.yang@mediatek•com>
Subject: Re: linux-next: build warning after merge of the pinctrl tree
Date: Wed, 20 May 2015 09:14:55 +0200 [thread overview]
Message-ID: <CACRpkdYrCf+FtNyGqBTFzYnL-S_fU09ZSp-VCZuXSH0RxGpsRA@mail.gmail.com> (raw)
In-Reply-To: <20150520164008.616458c6@canb.auug.org.au>
On Wed, May 20, 2015 at 8:40 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Linus,
>
> After merging the pinctrl tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> warning: (PINCTRL_MT6397) selects PINCTRL_MTK_COMMON which has unmet direct dependencies (PINCTRL && (ARCH_MEDIATEK || COMPILE_TEST) && OF)
>
> Introduced by commit fc59e66c4284 ("pinctrl: mediatek: Add Pinctrl/GPIO
> driver for mt6397").
Ah too bad I didn't see it before pushing, fixed it now, thanks!
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-05-20 7:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 6:40 linux-next: build warning after merge of the pinctrl tree Stephen Rothwell
2015-05-20 7:14 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 7:11 Stephen Rothwell
2022-04-21 14:12 ` Linus Walleij
2022-04-21 18:05 ` Stefan Wahren
2021-10-27 11:01 Stephen Rothwell
2021-10-27 11:10 ` Marc Zyngier
2021-10-28 7:03 ` Mauro Carvalho Chehab
2022-01-20 3:25 ` Stephen Rothwell
2022-03-18 7:31 ` Stephen Rothwell
2022-06-05 23:33 ` Stephen Rothwell
2021-03-30 6:07 Stephen Rothwell
2021-03-30 7:51 ` Linus Walleij
2020-04-17 2:27 Stephen Rothwell
2020-04-17 10:23 ` Linus Walleij
2018-10-11 3:17 Stephen Rothwell
2018-10-11 7:51 ` Linus Walleij
2017-06-30 4:56 Stephen Rothwell
2017-06-30 4:57 ` Stephen Rothwell
2017-06-30 6:59 ` Geert Uytterhoeven
2017-06-30 13:48 ` Linus Walleij
2017-01-03 4:37 Stephen Rothwell
2014-05-19 6:59 Stephen Rothwell
2014-05-19 9:03 ` Maxime Ripard
2013-12-13 4:06 Stephen Rothwell
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=CACRpkdYrCf+FtNyGqBTFzYnL-S_fU09ZSp-VCZuXSH0RxGpsRA@mail.gmail.com \
--to=linus.walleij@linaro$(echo .)org \
--cc=hongzhou.yang@mediatek$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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