Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ronnie Sahlberg <rsahlberg@ciq.com>
Cc: stable@vger.kernel.org
Subject: Re: Candidates for stable v6.9..v6.10-rc1 Deadlock
Date: Wed, 19 Jun 2024 14:05:27 +0200	[thread overview]
Message-ID: <2024061917-ruined-retype-2167@gregkh> (raw)
In-Reply-To: <CAK4epfz9B58Dfz=wwNP2PJQzeqvT3J_kjY9d7PNY_VPKDKE=dA@mail.gmail.com>

On Mon, Jun 03, 2024 at 04:48:56PM -0400, Ronnie Sahlberg wrote:
> These commits reference Deadlock between v6.9 and v6.10-rc1
> 
> These commits are not, yet, in stable/linux-rolling-stable.
> Let me know if you would rather me compare to a different repo/branch.
> The list has been manually pruned to only contain commits that look like
> actual issues.
> If they contain a Fixes line it has been verified that at least one of the
> commits that the Fixes tag(s) reference is in stable/linux-rolling-stable
> 
> 
> 56c35f43eef013579c76
> eec7620800081e27dbf8
> 4268254a39484fc11ba9
> 0a46ef234756dca04623
> ecf0b2b8a37c84641866
> e03a5d3e95f22d15d8df
> 4d3421e04c5dc38baf15
> 9cc6290991e6cfc9a644
> 77e619a82fc384ae3d1d

I just grabbed one of these at random, and this commit message says:
	This patch brings no functional change.

and in reading it, it's just a "let's quiet the tools for now, but
really, all is good".  So that's not something we should be applying,
right?

thanks,

greg k-h

      reply	other threads:[~2024-06-19 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 20:48 Candidates for stable v6.9..v6.10-rc1 Deadlock Ronnie Sahlberg
2024-06-19 12:05 ` 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=2024061917-ruined-retype-2167@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=rsahlberg@ciq.com \
    --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