[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZFjqKoZtgOAWrkP+@pengutronix.de>
Date: Mon, 8 May 2023 14:25:14 +0200
From: Sascha Hauer <s.hauer@...gutronix.de>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Jonathan Corbet <corbet@....net>, Pavel Machek <pavel@....cz>,
Lee Jones <lee@...nel.org>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 00/11] leds: introduce new LED hw control APIs
Hi Christian,
On Thu, Apr 27, 2023 at 02:15:30AM +0200, Christian Marangi wrote:
> This is a continue of [1]. It was decided to take a more gradual
> approach to implement LEDs support for switch and phy starting with
> basic support and then implementing the hw control part when we have all
> the prereq done.
I tried to apply this series to give it a try. To what tree should this
series be applied upon?
> [1] https://lore.kernel.org/lkml/20230216013230.22978-1-ansuelsmth@gmail.com/
>
> Changes from previous v8 series:
> - Rewrite Documentation from scratch and move to separate commit
> - Strip additional trigger modes (to propose in a different series)
> - Strip from qca8k driver additional modes (to implement in the different
> series)
> - Split the netdev chages to smaller piece to permit easier review
The changelog reads as if it should be applied instead of v8, but this
series doesn't apply on a vanilla kernel. For example, TRIGGER_NETDEV_TX
is moved around in this series, but not present in vanilla Linux.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists