From: Samuel Holland <samuel.holland@sifive.com>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] RISC-V: drop SOC_SIFIVE for ARCH_SIFIVE
Date: Mon, 11 Mar 2024 23:34:51 -0500 [thread overview]
Message-ID: <a4a55e1c-a7d7-4d56-936d-2cbff0fb2f20@sifive.com> (raw)
In-Reply-To: <20240305-praying-clad-c4fbcaa7ed0a@spud>
On 2024-03-05 12:37 PM, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> All the users in the kernel are gone and generated .config files from
> previous LTS kernels will contain ARCH_SIFIVE. Drop SOC_SIFIVE and
> update the defconfig.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> CC: Paul Walmsley <paul.walmsley@sifive.com>
> CC: Palmer Dabbelt <palmer@dabbelt.com>
> CC: Albert Ou <aou@eecs.berkeley.edu>
> CC: linux-riscv@lists.infradead.org
> CC: linux-kernel@vger.kernel.org
> ---
> arch/riscv/Kconfig.socs | 3 ---
> arch/riscv/configs/defconfig | 2 +-
> 2 files changed, 1 insertion(+), 4 deletions(-)
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
next prev parent reply other threads:[~2024-03-12 4:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 18:37 Conor Dooley
2024-03-05 18:37 ` [PATCH v1 2/2] RISC-V: drop SOC_VIRT for ARCH_VIRT Conor Dooley
2024-04-03 18:22 ` Palmer Dabbelt
2024-03-12 4:34 ` Samuel Holland [this message]
2024-04-03 18:22 ` [PATCH v1 1/2] RISC-V: drop SOC_SIFIVE for ARCH_SIFIVE Palmer Dabbelt
2024-04-10 10:44 ` Conor Dooley
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=a4a55e1c-a7d7-4d56-936d-2cbff0fb2f20@sifive.com \
--to=samuel.holland@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®