public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: Are the 'FAILED' notifications always sent?
Date: Wed, 12 Jun 2024 15:17:06 +0200	[thread overview]
Message-ID: <69942468-2a5e-4e26-b667-bb77c4750d9b@kernel.org> (raw)
In-Reply-To: <2024061229-colony-implicate-c906@gregkh>

Hi Greg,

Thank you for the reply!

On 12/06/2024 14:11, Greg KH wrote:
> On Mon, May 27, 2024 at 12:55:47PM +0200, Matthieu Baerts wrote:
>> Hi Sasha,
>>
>> Thank you for the recent backports linked to MPTCP.
>>
>> Recently, I noticed that two patches [1] [2] with the same "Fixes" tag
>> -- but without "Cc: stable", sorry for that -- have been backported to
>> different stable versions. That's good, thank you!
>>
>> The first patch made its way to v5.15, while the second one went up to
>> v6.8, but not to older stable versions. I understand it didn't go
>> further because of other conflicts, and I'm ready to help to fix them.
>>
>> I just wanted to know if it is normal I didn't get any 'FAILED'
>> notifications like the ones Greg send [3]: I rely on them to know which
>> patches have been treated by the Stable team, but had conflicts. Will I
>> get these notifications later (no hurry), or should I not rely on them
>> to track fixes that could not be backported?
> 
> FAILED only happens for patches that explicitly have a "Cc: stable@" tag
> in a commit.  If you only have a "Fixes:" tag, that doesn't happen as we
> read that as "best effort if the stable team wants to add it".

That's clear and it makes sense. I will make sure not to miss the "Cc:
stable@" tag next time.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2024-06-12 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 10:55 Are the 'FAILED' notifications always sent? Matthieu Baerts
2024-06-12 12:11 ` Greg KH
2024-06-12 13:17   ` Matthieu Baerts [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=69942468-2a5e-4e26-b667-bb77c4750d9b@kernel.org \
    --to=matttbe@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --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