[RFC 00/27] RISC-V: Convert SOC_FOO symbols to ARCH_FOO

[Geert Uytterhoeven]

Hi Conor,

On Tue, Sep 27, 2022 at 8:58 AM Conor Dooley <conor.dooley at microchip.com> wrote:
> On Tue, Sep 27, 2022 at 08:48:00AM +0200, Arnd Bergmann wrote:
> > On Tue, Sep 27, 2022, at 8:34 AM, Conor Dooley wrote:
> > > On Mon, Sep 26, 2022 at 11:04:58AM +0200, Geert Uytterhoeven wrote:
> > >
> > >> and (b) you take this through the RISC-V tree, you will miss all newly
> > >> introduced users in other subsystem trees.
> > >
> > > Aye, your suggested timing makes sense, but there are quite a few
> > > subsystems involved here, so maybe doing it at the very end of the
> > > window rather than asking everyone to stall until rc2 may be more
> > > feasible?
> >
> > Since there is no rush here, maybe stage this out over two releases?
> > At first, just introduce the new symbols as aliases like
> >
> > config ARCH_FOO
> >       def_bool SOC_FOO
> >
> > then change all the drivers in the following cycle after the syumbol
> > exists, and finally rename the user-visible symbols and remove the
> > old version.
> >
>
> I think I suggested that at LPC but was told not to bother, which is why
> I did a direct conversion. I'd prefer to do it your suggested way
> though & I think I will do it that way for a v1.

This way has the added advantage that "make oldconfig" keeps on working
(assumed no one skips one release ;-)

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