[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_VchfzoKOTvy5TQ@shell.armlinux.org.uk>
Date: Tue, 8 Apr 2025 18:27:33 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Sean Anderson <sean.anderson@...ux.dev>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
linux-kernel@...r.kernel.org, upstream@...oha.com,
Christian Marangi <ansuelsmth@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Kory Maincent <kory.maincent@...tlin.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Clark Wang <xiaoning.wang@....com>,
Claudiu Beznea <claudiu.beznea@...rochip.com>,
Claudiu Manoil <claudiu.manoil@....com>,
Conor Dooley <conor+dt@...nel.org>,
Ioana Ciornei <ioana.ciornei@....com>,
Jonathan Corbet <corbet@....net>, Joyce Ooi <joyce.ooi@...el.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Madalin Bucur <madalin.bucur@....com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Michal Simek <michal.simek@....com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@....com>,
Rob Herring <robh+dt@...nel.org>, Rob Herring <robh@...nel.org>,
Robert Hancock <robert.hancock@...ian.com>,
Saravana Kannan <saravanak@...gle.com>,
UNGLinuxDriver@...rochip.com,
Vladimir Oltean <vladimir.oltean@....com>,
Wei Fang <wei.fang@....com>, devicetree@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-doc@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com
Subject: Re: [net-next PATCH v2 00/14] Add PCS core support
On Tue, Apr 08, 2025 at 11:30:43AM -0400, Sean Anderson wrote:
> On 4/8/25 10:50, Jakub Kicinski wrote:
> > On Mon, 7 Apr 2025 19:17:31 -0400 Sean Anderson wrote:
> >> This series depends on [1,2], and they have been included at the
> >> beginning so CI will run. However, I expect them to be reviewed/applied
> >> outside the net-next tree.
> >
> > These appear to break the build:
> >
> > drivers/acpi/property.c:1669:39: error: initialization of ‘int (*)(const struct fwnode_handle *, const char *, const char *, int, unsigned int, struct fwnode_reference_args *)’ from incompatible pointer type ‘int (*)(const struct fwnode_handle *, const char *, const char *, unsigned int, unsigned int, struct fwnode_reference_args *)’ [-Wincompatible-pointer-types]
> > 1669 | .get_reference_args = acpi_fwnode_get_reference_args, \
> >
> > Could you post as RFC until we can actually merge this? I'm worried
> > some sleep deprived maintainer may miss the note in the cover letter
> > and just apply it all to net-next..
>
> I would really like to keep RFC off the titles since some reviewers don't
> pay attention to RFC series.
>
> Would [DO NOT MERGE] in the subject be OK?
I'd bet that those who have decided "RFC means the patch series is not
ready" will take such a notice to also mean the same, and ignore it.
I think there needs to be some kind of push-back against these
maintainers who explicitly state that they ignore RFC series - making
it basically anti-social behaviour in the kernel community.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists