From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] USB/Thunderbolt/PHY patches for 5.6-rc1
Date: Wed, 29 Jan 2020 20:42:33 +0100 [thread overview]
Message-ID: <20200129194233.GA578620@kroah.com> (raw)
In-Reply-To: <CAHk-=wgwBfz0CtAFZMDy=A_Wz0+=dzrfWWiHESUD9CxnV=Xyjw@mail.gmail.com>
On Wed, Jan 29, 2020 at 10:11:26AM -0800, Linus Torvalds wrote:
> On Wed, Jan 29, 2020 at 2:14 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Here is the big USB and Thunderbolt and PHY driver updates for 5.6-rc1.
>
> Hmm. This actually causes a new warning even before I start building it:
>
> WARNING: unmet direct dependencies detected for I2C_S3C2410
> Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && HAVE_S3C2410_I2C [=n]
> Selected by [m]:
> - PHY_EXYNOS5250_SATA [=m] && (SOC_EXYNOS5250 || COMPILE_TEST
> [=y]) && HAS_IOMEM [=y] && OF [=y]
>
> and the cause seems to be
>
> 203b7ee14d3a ("phy: Enable compile testing for some of drivers")
>
> where PHY_EXYNOS5250_SATA now has a
>
> depends on SOC_EXYNOS5250 || COMPILE_TEST
> depends on HAS_IOMEM
> depends on OF
>
> and then blindly does a
>
> select I2C_S3C2410
>
> without having the dependencies that I2C_S3C2410 has.
>
> How did this ever pass any testing in linux-next without being
> noticed, when I noticed within five seconds of pulling it? It
> literally warns immediately on "make allmodconfig".
linux-next was fine as the fix was in the i2c tree. Sorry for not
realizing it here as well, it didn't show up on my test builds as I
wasn't doing 'allmodconfig' for USB stuff.
If it's any consolation, it was a lot worse, I did take some fixups for
other issues like this that came in through here :)
But I should have caught this as well, sorry, and thanks for merging.
greg k-h
next prev parent reply other threads:[~2020-01-29 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 10:14 [GIT PULL] USB/Thunderbolt/PHY patches for 5.6-rc1 Greg KH
2020-01-29 18:11 ` Linus Torvalds
2020-01-29 18:20 ` Krzysztof Kozlowski
2020-01-29 18:23 ` Linus Torvalds
2020-01-29 18:27 ` Krzysztof Kozlowski
2020-01-29 19:42 ` Greg KH [this message]
2020-01-29 21:34 ` Stephen Rothwell
2020-01-30 10:52 ` Felipe Balbi
2020-01-29 19:00 ` pr-tracker-bot
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=20200129194233.GA578620@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox