[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <834F56B9-E394-4F7C-97D8-BAA97F03362E@kernel.org>
Date: Sun, 09 Apr 2023 09:58:42 +0100
From: Conor Dooley <conor@...nel.org>
To: linux-riscv@...ts.infradead.org,
Christoph Hellwig <hch@...radead.org>
CC: Conor Dooley <conor.dooley@...rochip.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Rob Herring <robh@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH v1 0/4] Convert SiFive drivers from SOC_FOO dependencies to ARCH_FOO
On 8 April 2023 06:47:59 IST, Christoph Hellwig <hch@...radead.org> wrote:
>On Thu, Apr 06, 2023 at 09:57:46PM +0100, Conor Dooley wrote:
>> From: Conor Dooley <conor.dooley@...rochip.com>
>>
>> RISC-V's SOC_FOO symbols for micro-archs are going away, and being
>> replaced with the more common ARCH_FOO pattern that is used by other
>> archs (and by vendors with a history outside of RISC-V).
>
>And this is still the wrong way around. This ARCH_ madness must not
>spread. NAK.
As I said when you complained last, we asked the arm lads and there was no interest there in doing things differently & that's just one architecture.
Nor was there in adding a SOC_ symbol from some of the people who do more than one ISA.
You're welcome to send reverts for my first round of conversions and patches converting all the ARCH_ stuff RISC-V has to SOC_.
I'll happily ack a complete conversion to SOC_.
I don't care if it is arch or soc, I just want things to be used consistently.
Powered by blists - more mailing lists