From: Krzysztof Kozlowski <krzk@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Wolfram Sang <wsa@the-dreams.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Jan 23 (PHY_EXYNOS5250_SATA in drivers/phy/samsung/Kconfig)
Date: Thu, 23 Jan 2020 09:03:02 +0100 [thread overview]
Message-ID: <CAJKOXPcJ8V+bLDeJGg+emCaYHtDjuKa--yMk_HRCsB_DrwJGrw@mail.gmail.com> (raw)
In-Reply-To: <beb9e3a3-4824-6328-12f8-3d005f376374@infradead.org>
On Thu, 23 Jan 2020 at 08:00, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 1/22/20 10:21 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200122:
> >
>
> Is linux-next missing some of the COMPILE_TEST fixes? I am still seeing
> this warning (that I reported on Jan. 9-2020 and that Arnd has sent a
> possible patch for):
>
>
> on i386 or x86_64:
>
> WARNING: unmet direct dependencies detected for I2C_S3C2410
> Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && HAVE_S3C2410_I2C [=n]
> Selected by [y]:
> - PHY_EXYNOS5250_SATA [=y] && (SOC_EXYNOS5250 || COMPILE_TEST [=y]) && HAS_IOMEM [=y] && OF [=y]
Hi Randy,
The fix was posted quite some time ago - next to the patches
(unfortunately) introducing the issue. I posted v2, after review, on
7th of January:
https://lore.kernel.org/linux-arm-kernel/1578384779-15487-1-git-send-email-krzk@kernel.org/T/#t
Maybe I missed someone on Cc there?
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-01-23 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 6:21 linux-next: Tree for Jan 23 Stephen Rothwell
2020-01-23 7:00 ` linux-next: Tree for Jan 23 (PHY_EXYNOS5250_SATA in drivers/phy/samsung/Kconfig) Randy Dunlap
2020-01-23 8:03 ` Krzysztof Kozlowski [this message]
2020-01-23 8:59 ` Randy Dunlap
2020-01-23 9:09 ` Wolfram Sang
2020-01-23 8:44 ` linux-next: Tree for Jan 23 (gpu/drm/panel/) Randy Dunlap
2020-01-23 19:49 ` Sam Ravnborg
2020-01-23 23:46 ` Randy Dunlap
2020-01-24 0:16 ` 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=CAJKOXPcJ8V+bLDeJGg+emCaYHtDjuKa--yMk_HRCsB_DrwJGrw@mail.gmail.com \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).