From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: <john.garry@huawei.com>, <rdunlap@infradead.org>,
<sfr@canb.auug.org.au>, <linux-next@vger.kernel.org>,
<joe@perches.com>, <broonie@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 10 (mtd/spi-nor/)
Date: Wed, 11 Mar 2020 07:12:32 +0000 [thread overview]
Message-ID: <1993805.xNpbgTSjYd@localhost.localdomain> (raw)
In-Reply-To: <f9d33b09-fe9f-2c26-96dc-b2eaa53c614b@huawei.com>
On Tuesday, March 10, 2020 7:14:13 PM EET John Garry wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> +
>
> On 10/03/2020 14:37, Randy Dunlap wrote:
> > On 3/10/20 2:19 AM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20200306:
> >>
> >> Removed tree: nfc-next (abanboned)
> >>
> > doned
> >
> > on i386:
> >
> > WARNING: unmet direct dependencies detected for MTD_SPI_NOR
>
> Uh, so kbuild honors a "select" of a config option which has unmet
> dependencies:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu
> mentation/kbuild/kconfig-language.rst?h=v5.6-rc5#n143
>
> So this looks introduced by:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/d
> rivers/spi/Kconfig?h=next-20200310&id=e14572c52546c16e159c4c1814984843a119e8
Hi, John,
Is there any need to select the MTD_SPI_NOR in SPI_HISI_SFC_V3XX? Can't we
just drop the select?
Cheers,
ta
next prev parent reply other threads:[~2020-03-11 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 9:19 linux-next: Tree for Mar 10 Stephen Rothwell
2020-03-10 14:37 ` linux-next: Tree for Mar 10 (mtd/spi-nor/) Randy Dunlap
2020-03-10 17:14 ` John Garry
2020-03-10 20:36 ` Randy Dunlap
2020-03-11 2:20 ` Randy Dunlap
2020-03-11 7:12 ` Tudor.Ambarus [this message]
2020-03-11 7:56 ` John Garry
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=1993805.xNpbgTSjYd@localhost.localdomain \
--to=tudor.ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=joe@perches.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@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