[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200626.132101.413123758768311075.davem@davemloft.net>
Date: Fri, 26 Jun 2020 13:21:01 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jbx6244@...il.com
Cc: peppe.cavallaro@...com, alexandre.torgue@...com,
joabreu@...opsys.com, kuba@...nel.org, mcoquelin.stm32@...il.com,
heiko@...ech.de, linux-rockchip@...ts.infradead.org,
netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] net: stmmac: change Kconfig menu entry to
STMMAC/DWMAC
From: Johan Jonker <jbx6244@...il.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@...il.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.
Powered by blists - more mailing lists