[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6471ea12.050a0220.14fde.15f2@mx.google.com>
Date: Sat, 27 May 2023 13:31:28 +0200
From: Christian Marangi <ansuelsmth@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Jonathan Corbet <corbet@....net>, 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>, Paolo Abeni <pabeni@...hat.com>,
linux-leds@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [net-next PATCH v2 00/13] leds: introduce new LED hw control APIs
On Thu, May 25, 2023 at 08:43:38PM -0700, Jakub Kicinski wrote:
> On Thu, 25 May 2023 16:53:48 +0200 Christian Marangi wrote:
> > This is based on top of branch ib-leds-netdev-v6.5 present here [1].
>
> I merged that PR now, but you'll need to repost.
> Build bots don't read English (yet?) so posting patches which can't
> be immediately applied is basically an RFC (and should be marked as
> such).
Hi, thanks for helping in this! The series already applied directly on
net-next but I sent v3 anyway rebased on latest commit from net-next
just to be sure.
--
Ansuel
Powered by blists - more mailing lists