[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9624f27a-8dd2-4e99-9f31-eff9b581d3fa@lunn.ch>
Date: Thu, 13 Mar 2025 15:40:39 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marek BehĂșn <kabel@...nel.org>
Cc: Vladimir Oltean <olteanv@...il.com>,
"Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
Vivien Didelot <vivien.didelot@...il.com>,
Tobias Waldekranz <tobias@...dekranz.com>, netdev@...r.kernel.org,
Lev Olshvang <lev_o@....com>
Subject: Re: [PATCH net 08/13] net: dsa: mv88e6xxx: enable .rmu_disable() for
6320 family
On Thu, Mar 13, 2025 at 02:41:41PM +0100, Marek BehĂșn wrote:
> Commit 9e5baf9b3636 ("net: dsa: mv88e6xxx: add RMU disable op") forgot
> to add the .rmu_disable() method for the 6320 family. Fix it.
Please add a justification for stable. The rules say:
It must either fix a real bug that bothers people or just add a
device ID.
How does this bother people?
Please look through all the patches in this set and split them between
net and net-next. They do not all meet this requirement.
Andrew
---
pw-bot: cr
Powered by blists - more mailing lists