From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Greg KH <greg@kroah.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: linux-next: build warnings after merge of the usb tree
Date: Tue, 21 Jan 2020 08:55:27 +0100 [thread overview]
Message-ID: <CAJKOXPdUhCfrq1xSvPGjAOZDr29YGTK2j_fYSGJ9xchFDE=cmQ@mail.gmail.com> (raw)
In-Reply-To: <20200121172823.62617483@canb.auug.org.au>
On Tue, 21 Jan 2020 at 07:28, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> On Tue, 7 Jan 2020 09:06:01 +0100 Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > On Tue, 7 Jan 2020 at 04:31, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> > > produced these warnings:
> > >
> > > 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]
> > >
> > > 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]
> > >
> > > 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]
> > >
> > > Introduced by commit
> > >
> > > 203b7ee14d3a ("phy: Enable compile testing for some of drivers")
> >
> > The fix is here:
> > https://lore.kernel.org/lkml/CAMuHMdUXJo3=x32xbfSUXs3O3JHaFpfxt0mHupEb+vzi=5+S4g@mail.gmail.com/
> > i2c: Enable compile testing for some of drivers
> > Although I need to send v2 of it.
>
> I am still seeing these warnings.
v2 is here:
https://lore.kernel.org/linux-arm-kernel/1578384779-15487-1-git-send-email-krzk@kernel.org/T/#t
Can someone review and/or pick it up?
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-01-21 7:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 3:30 linux-next: build warnings after merge of the usb tree Stephen Rothwell
2020-01-07 8:06 ` Krzysztof Kozlowski
2020-01-21 6:28 ` Stephen Rothwell
2020-01-21 7:55 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-17 7:57 Stephen Rothwell
2020-03-17 13:45 ` Andrey Konovalov
2020-03-17 13:53 ` Greg KH
2017-11-02 4:10 Stephen Rothwell
2017-11-02 8:45 ` Greg KH
2011-04-14 4:18 Stephen Rothwell
2011-04-14 4:51 ` Greg KH
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='CAJKOXPdUhCfrq1xSvPGjAOZDr29YGTK2j_fYSGJ9xchFDE=cmQ@mail.gmail.com' \
--to=krzk@kernel.org \
--cc=greg@kroah.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@the-dreams.de \
/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).