[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231211084656.26578d89@kernel.org>
Date: Mon, 11 Dec 2023 08:46:56 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Christian Marangi <ansuelsmth@...il.com>,
Lee Jones <lee@...nel.org>
Cc: Pavel Machek <pavel@....cz>, Andrew Lunn <andrew@...n.ch>,
Marek BehĂșn <kabel@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Li Zetao <lizetao1@...wei.com>, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org, Daniel Golle <daniel@...rotopia.org>
Subject: Re: [PATCH v3 1/2] leds: trigger: netdev: extend speeds up to 10G
On Mon, 11 Dec 2023 16:57:15 +0100 Christian Marangi wrote:
> > [1/2] leds: trigger: netdev: extend speeds up to 10G
> > commit: bc8e1da69a68d9871773b657d18400a7941cbdef
> > [2/2] docs: ABI: sysfs-class-led-trigger-netdev: add new modes and entry
> > commit: f07894d3b384344c43be1bcf61ef8e2fded0efe5
> >
>
> Hi, Lee
>
> I'm working on adding LEDs support for qca8081 PHY. This PHY supports
> 2500 link speed.
>
> Is it possible to have an immutable branch for this series so we can
> have this in net-next?
>
> Jakub can you also help with this?
I'm guessing that if it's already applied - it's already applied.
Lee, we seem to be getting quite a few LEDs/netdev patches - do you
reckon we should ask Konstantin for a separate repo to which we can
both apply, and then merge that into our respective trees? Because
stacking the changes on stable branches may get weird and/or error
prone. Or is separate tree an overkill at this stage? IDK..
Powered by blists - more mailing lists