[PATCH v1 1/7] RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols
Geert Uytterhoeven
geert at linux-m68k.org
Tue Jan 10 23:50:37 PST 2023
Hi Damien,
On Tue, Jan 10, 2023 at 11:47 PM Damien Le Moal
<damien.lemoal at opensource.wdc.com> wrote:
> On 1/11/23 07:34, Conor Dooley wrote:
> > On Wed, Jan 11, 2023 at 07:22:47AM +0900, Damien Le Moal wrote:
> >> By the way, I recall some pushback with the renaming of SOC_XXX to
> >> ARCH_XXX. I personally do not like it and Christoph suggested the revers
> >> approach of renaming arm ARCH_XXX to something else instead. I did not
> >> follow further on that discussion, but it looks like the riscv SOC_XXX
> >> renaming went through ?
> >
> > We asked the ARM guys about it, I think on IRC as they'd not replied to
> > the thread, and cold water was poured on the idea.
>
> That is really too bad. Naming something ARCH_XXX that is not a CPU
> architecture is simply very confusing I think.
I agree it is.
However, fixing that means adding backwards-compatiblity symbols,
updating the few thousand existing users, and dropping the old symbols.
And handling all the fall-out of people who didn't run "make oldconfig"
in between, now wondering why their kernel no longer boots.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
More information about the linux-riscv
mailing list