From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Colin Foster <colin.foster@in-advantage.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v4 net-next 5/5] net: mscc: ocelot: expose ocelot wm functions
Date: Tue, 7 Dec 2021 11:48:52 +0000 [thread overview]
Message-ID: <Ya9KJAYEypSs6+dO@shell.armlinux.org.uk> (raw)
In-Reply-To: <20211206180922.1efe4e51@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Mon, Dec 06, 2021 at 06:09:22PM -0800, Jakub Kicinski wrote:
> On Sat, 4 Dec 2021 10:28:58 -0800 Colin Foster wrote:
> > Expose ocelot_wm functions so they can be shared with other drivers.
> >
> > Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> > Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> Yeah.. but there are no in-tree users of these. What's the story?
>
> I see Vladimir reviewed this so presumably we trust that the users
> will materialize rather quickly?
Thank you for highlighting this.
Vladimir told me recently over the phylink get_interfaces vs get_caps
change for DSA, and I quote:
David who applied your patch can correct me, but my understanding from
the little time I've spent on netdev is that dead code isn't a candidate
for getting accepted into the tree, even more so in the last few days
before the merge window, from where it got into v5.16-rc1.
...
So yes, I take issue with that as a matter of principle, I very much
expect that a kernel developer of your experience does not set a
precedent and a pretext for people who submit various shady stuff to the
kernel just to make their downstream life easier.
This sounds very much like double-standards, especially as Vladimir
reviewed this.
I'm not going to be spiteful NAK these patches, because we all need to
get along with each other. I realise that it is sometimes useful to get
code merged that facilitates or aids further development - provided
that development is submitted in a timely manner.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-12-07 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 18:28 [PATCH v4 net-next 0/5] prepare ocelot for external interface control Colin Foster
2021-12-04 18:28 ` [PATCH v4 net-next 1/5] net: dsa: ocelot: remove unnecessary pci_bar variables Colin Foster
2021-12-04 18:28 ` [PATCH v4 net-next 2/5] net: dsa: ocelot: felix: Remove requirement for PCS in felix devices Colin Foster
2021-12-04 18:28 ` [PATCH v4 net-next 3/5] net: dsa: ocelot: felix: add interface for custom regmaps Colin Foster
2021-12-04 18:28 ` [PATCH v4 net-next 4/5] net: mscc: ocelot: split register definitions to a separate file Colin Foster
2021-12-04 18:28 ` [PATCH v4 net-next 5/5] net: mscc: ocelot: expose ocelot wm functions Colin Foster
2021-12-07 2:09 ` Jakub Kicinski
2021-12-07 11:48 ` Russell King (Oracle) [this message]
2021-12-07 12:11 ` Vladimir Oltean
2021-12-07 15:26 ` Jakub Kicinski
2021-12-07 15:30 ` Vladimir Oltean
2021-12-07 15:39 ` Jakub Kicinski
2021-12-07 16:40 ` Colin Foster
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=Ya9KJAYEypSs6+dO@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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