From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: mmotm 2020-01-09-17-33 uploaded (PHY_EXYNOS5250_SATA)
Date: Thu, 9 Jan 2020 21:03:30 -0800 [thread overview]
Message-ID: <19fac75f-ad09-dbf5-1d11-6e91c759aa02@infradead.org> (raw)
In-Reply-To: <20200110013413.NNeLcxiMi%akpm@linux-foundation.org>
On 1/9/20 5:34 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2020-01-09-17-33 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
on i386:
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]
I also notice that PHY_EXYNOS5250_SATA also selects I2C.
It is preferable not to select an entire subsystem. If a user wants a subsystem
enabled, then the user should enable it. This driver should instead depend on I2C.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-01-10 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 1:34 mmotm 2020-01-09-17-33 uploaded akpm
2020-01-10 5:03 ` Randy Dunlap [this message]
2020-01-10 6:57 ` mmotm 2020-01-09-17-33 uploaded (drivers/gpu/drm/i915/gt/intel_ggtt.c) Randy Dunlap
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=19fac75f-ad09-dbf5-1d11-6e91c759aa02@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=kishon@ti.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).