From: David Miller <davem@davemloft.net>
To: jbx6244@gmail.com
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
joabreu@synopsys.com, kuba@kernel.org, mcoquelin.stm32@gmail.com,
heiko@sntech.de, linux-rockchip@lists.infradead.org,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] net: stmmac: change Kconfig menu entry to STMMAC/DWMAC
Date: Fri, 26 Jun 2020 13:21:01 -0700 (PDT) [thread overview]
Message-ID: <20200626.132101.413123758768311075.davem@davemloft.net> (raw)
In-Reply-To: <20200626120527.10562-1-jbx6244@gmail.com>
From: Johan Jonker <jbx6244@gmail.com>
Date: Fri, 26 Jun 2020 14:05:26 +0200
> When a Rockchip user wants to enable support for
> the ethernet controller one has to search for
> something with STMicroelectronics.
> Change the Kconfig menu entry to STMMAC/DWMAC,
> so that it better reflects the options it enables.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
I'm not OK with this. It's called internally stmmac
beause it's based upon an ST Microelectronics chipset.
This is what happens when we have several sub drivers
based upon a top-level common chipset "library".
The problem you have is that just knowing the driver
doesn't tell you the dependencies, but that's a larger
scope generic problem that needs a high level solution
rather then something we should be hacking around with
name adjustments here and there.
prev parent reply other threads:[~2020-06-26 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 12:05 [PATCH 1/2] net: stmmac: change Kconfig menu entry to STMMAC/DWMAC Johan Jonker
2020-06-26 12:05 ` [PATCH 2/2] net: stmmac: add Rockchip as supported platform in STMMAC_PLATFORM help text Johan Jonker
2020-06-26 20:21 ` David Miller [this message]
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=20200626.132101.413123758768311075.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).