[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YnU17/cVA0i3UStL@kroah.com>
Date: Fri, 6 May 2022 16:51:27 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Francesco Dolcini <francesco.dolcini@...adex.com>
Cc: stable@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Joakim Zhang <qiangqing.zhang@....com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net v2] net: phy: Fix race condition on link status change
On Fri, May 06, 2022 at 12:10:31PM +0200, Francesco Dolcini wrote:
> Hello,
> I have one question about the process of patch/fixes backporting
> to old stable kernel.
>
> Assuming the following patch will be deemed correct and applied it will
> have to be eventually backported.
>
> This patch will apply cleanly on v5.15+, but some work is needed to
> backport to v5.10 or older.
>
> Should I send a patch for the older kernels once the fix is merged?
> Reading Documentation/process/stable-kernel-rules.rst it was not clear
> to me what to do in this "mixed" situations.
You will get an email from me if it does not apply to older kernels and
you can respond with the backported fix then.
thanks,
greg k-h
Powered by blists - more mailing lists