From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.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: Wed, 10 Apr 2024 11:44:15 +0100 [thread overview]
Message-ID: <20240410-scarce-lyrically-63677063159d@spud> (raw)
In-Reply-To: <20240305-praying-clad-c4fbcaa7ed0a@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Tue, 05 Mar 2024 18:37:05 +0000, Conor Dooley wrote:
> 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.
>
>
Applied to riscv-soc-for-next, thanks!
[1/2] RISC-V: drop SOC_SIFIVE for ARCH_SIFIVE
https://git.kernel.org/conor/c/d2a351e63779
[2/2] RISC-V: drop SOC_VIRT for ARCH_VIRT
https://git.kernel.org/conor/c/1553a1c48281
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-04-10 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 18:37 [PATCH v1 1/2] RISC-V: drop SOC_SIFIVE for ARCH_SIFIVE 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 ` [PATCH v1 1/2] RISC-V: drop SOC_SIFIVE for ARCH_SIFIVE Samuel Holland
2024-04-03 18:22 ` Palmer Dabbelt
2024-04-10 10:44 ` Conor Dooley [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=20240410-scarce-lyrically-63677063159d@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--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