[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdViDiR+rfzH8VeHxOx0cZHaw27CUE5PRwxaQuaWmbWu=w@mail.gmail.com>
Date: Tue, 24 Oct 2023 15:04:05 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-renesas-soc@...r.kernel.org,
Niklas Söderlund <niklas.soderlund@...natech.se>,
Sergey Shtylyov <s.shtylyov@....ru>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 2/2] net: ethernet: renesas: drop SoC names in Kconfig
Hi Paolo,
On Tue, Oct 24, 2023 at 12:54 PM Paolo Abeni <pabeni@...hat.com> wrote:
> On Sun, 2023-10-22 at 22:53 +0200, Wolfram Sang wrote:
> > Mentioning SoCs in Kconfig descriptions tends to get stale (e.g. RAVB is
> > missing RZV2M) or imprecise (e.g. SH_ETH is not available on all
> > R8A779x). Drop them instead of providing vague information. Improve the
> > file description a tad while here.
>
> It's not a big deal, but assuming that keeping the SoC list up2date
> requires too much effort, I would still keep it, with some additional
> wording specifying it's partial and potentially inaccurate.
Apparently it was too much effort...
> Such list could be an useful starting point for an integrator looking
> for the correct driver for his/her SoC.
For modern DT-based systems, it's much easier to look up compatible
values.
See also scripts/dtc/dt_to_config.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
Powered by blists - more mailing lists