From: Andreas Schwab <schwab@linux-m68k.org>
To: Anup Patel <anup@brainfault.org>
Cc: Sagar Kadam <sagar.kadam@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"tudor.ambarus@microchip.com" <tudor.ambarus@microchip.com>,
"richard@nod.at" <richard@nod.at>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 1/2] riscv: defconfig: enable spi nor on Hifive Unleashed A00 board.
Date: Wed, 06 May 2020 09:26:44 +0200 [thread overview]
Message-ID: <87d07h8qx7.fsf@igel.home> (raw)
In-Reply-To: <CAAhSdy2-ECrOP=kZOTXxj1t+f8NrcYjbXKDRwPB3KU36mDmWWg@mail.gmail.com> (Anup Patel's message of "Wed, 6 May 2020 10:39:39 +0530")
On Mai 06 2020, Anup Patel wrote:
> We had build issues in past by selecting major driver subsystems
> in Kconfig.socs
>
> I suggest to select SPI_SIFIVE from Kconfig.socs
SPI_SIFIVE can be m, don't override that.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-05-06 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:58 [PATCH 0/2] update is25wp256d page write capabilities Sagar Shrikant Kadam
2020-04-30 9:58 ` [PATCH 1/2] riscv: defconfig: enable spi nor on Hifive Unleashed A00 board Sagar Shrikant Kadam
2020-05-04 22:10 ` Palmer Dabbelt
2020-05-05 7:18 ` Sagar Kadam
2020-05-05 23:23 ` Palmer Dabbelt
2020-05-06 3:56 ` Sagar Kadam
2020-05-06 5:09 ` Anup Patel
2020-05-06 7:26 ` Andreas Schwab [this message]
2020-05-10 15:32 ` Sagar Kadam
2020-04-30 9:58 ` [PATCH 2/2] spi: nor: update page program settings for is25wp256 using post bfpt fixup Sagar Shrikant Kadam
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=87d07h8qx7.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=anup@brainfault.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richard@nod.at \
--cc=sagar.kadam@sifive.com \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
/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