From: Paolo Abeni <pabeni@redhat.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Sergey Shtylyov" <s.shtylyov@omp.ru>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: ethernet: renesas: drop SoC names in Kconfig
Date: Tue, 24 Oct 2023 12:53:26 +0200 [thread overview]
Message-ID: <b0b4054adcb5250ad49e19d8f90c89de802f0125.camel@redhat.com> (raw)
In-Reply-To: <20231022205316.3209-3-wsa+renesas@sang-engineering.com>
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.
Such list could be an useful starting point for an integrator looking
for the correct driver for his/her SoC.
Cheers,
Paolo
next prev parent reply other threads:[~2023-10-24 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 20:53 [PATCH net-next 0/2] net: ethernet: renesas: infrastructure preparations for upcoming driver Wolfram Sang
2023-10-22 20:53 ` [PATCH net-next 1/2] net: ethernet: renesas: group entries in Makefile Wolfram Sang
2023-10-23 8:45 ` Sergey Shtylyov
2023-10-23 9:12 ` Wolfram Sang
2023-10-22 20:53 ` [PATCH net-next 2/2] net: ethernet: renesas: drop SoC names in Kconfig Wolfram Sang
2023-10-23 8:48 ` Sergey Shtylyov
2023-10-24 10:53 ` Paolo Abeni [this message]
2023-10-24 13:04 ` Geert Uytterhoeven
2023-10-23 8:51 ` [PATCH net-next 0/2] net: ethernet: renesas: infrastructure preparations for upcoming driver Niklas Söderlund
2023-10-24 23:30 ` patchwork-bot+netdevbpf
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=b0b4054adcb5250ad49e19d8f90c89de802f0125.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=s.shtylyov@omp.ru \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).