From: Vignesh Raghavendra <vigneshr@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-fsdevel@vger.kernel.org>
Cc: <akpm@linux-foundation.org>, <broonie@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>,
<linux-mtd@lists.infradead.org>
Subject: Re: mmotm 2019-07-17-16-05 uploaded (MTD_HYPERBUS, HBMC_AM654)
Date: Fri, 19 Jul 2019 14:02:47 +0530 [thread overview]
Message-ID: <c3b93f7a-5861-475f-faeb-3ec7e8e9b728@ti.com> (raw)
In-Reply-To: <4b510069-5f5d-d079-1a98-de190321a97a@infradead.org>
Hi,
On 18/07/19 9:15 PM, Randy Dunlap wrote:
> On 7/17/19 4:06 PM, akpm@linux-foundation.org wrote:
>> The mm-of-the-moment snapshot 2019-07-17-16-05 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 x86_64, when CONFIG_OF is not set/enabled:
>
> WARNING: unmet direct dependencies detected for MUX_MMIO
> Depends on [n]: MULTIPLEXER [=y] && (OF [=n] || COMPILE_TEST [=n])
> Selected by [y]:
> - HBMC_AM654 [=y] && MTD [=y] && MTD_HYPERBUS [=y]
>
> due to
> config HBMC_AM654
> tristate "HyperBus controller driver for AM65x SoC"
> select MULTIPLEXER
> select MUX_MMIO
>
> Those unprotected selects are lacking something.
>
Sorry for that! I have posted a fix here. Let me know if that works. Thanks!
https://patchwork.ozlabs.org/patch/1133946/
--
Regards
Vignesh
prev parent reply other threads:[~2019-07-19 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 23:06 mmotm 2019-07-17-16-05 uploaded akpm
2019-07-18 3:21 ` Stephen Rothwell
2019-07-18 15:45 ` mmotm 2019-07-17-16-05 uploaded (MTD_HYPERBUS, HBMC_AM654) Randy Dunlap
2019-07-19 8:32 ` Vignesh Raghavendra [this message]
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=c3b93f7a-5861-475f-faeb-3ec7e8e9b728@ti.com \
--to=vigneshr@ti.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.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