Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: stable@vger.kernel.org
Subject: Re: Missing backport for 04361b8bb818 ("net: sfp: fix state loss when updating state_hw_mask")
Date: Sun, 11 Jun 2023 09:24:54 +0200	[thread overview]
Message-ID: <2023061137-algorithm-almanac-1337@gregkh> (raw)
In-Reply-To: <99df4175-f41a-47d1-9d55-99e1976e8127@lunn.ch>

On Sun, Jun 11, 2023 at 12:37:11AM +0200, Andrew Lunn wrote:
> Hi Greg, Sasha
> 
> Commit 04361b8bb818 ("net: sfp: fix state loss when updating state_hw_mask")
> 
> ends with:
> 
>     Fixes: 8475c4b70b04 ("net: sfp: re-implement soft state polling setup")
> 
> git tag --contains 8475c4b70b04
> 
> shows that the problem was introduced in v6.1-rc1. However, the fix
> has not been backported yet to v6.1.X
> 
> Is the Fixes: tag not sufficient to trigger the machinery to get it
> back ported?

Not at all!  Please see the rules at:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

A "bare" Fixes: tag never guarantees that it will ever go to a stable
tree, you MUST put a cc: stable on it in order to make sure that
happens.

It's been that way for 18+ years now, nothing new :)

> Please could you back port it. It cleanly cherry-picks to v6.1.33

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-06-11  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 22:37 Missing backport for 04361b8bb818 ("net: sfp: fix state loss when updating state_hw_mask") Andrew Lunn
2023-06-11  7:24 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023061137-algorithm-almanac-1337@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox