public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: MPTCP stable backports: is the workflow OK?
Date: Sat, 7 Sep 2024 11:43:06 -0400	[thread overview]
Message-ID: <Ztx0ii15ulDATpUK@sashalap> (raw)
In-Reply-To: <be29b0d9-83be-4947-912e-8d9f5b8f5f9c@kernel.org>

On Fri, Sep 06, 2024 at 12:10:22PM +0200, Matthieu Baerts wrote:
>Hi Greg, Sasha,
>
>Thank you for your reply!
>
>On 06/09/2024 11:56, Greg KH wrote:
>> On Fri, Sep 06, 2024 at 11:36:25AM +0200, Matthieu Baerts wrote:
>>> Hi Greg,
>>>
>>> Thank you again for your support when we send patches for stable
>>> versions for MPTCP!
>>>
>>> Recently, I sent many patches for the stable versions, and I just wanted
>>> to check if what I did was OK for you?
>>>
>>> I tried to reply to all the 'FAILED: patch' emails you sent, either with
>>> patches, or with reasons explaining why it is fine not to backport them.
>>> Are you OK with that?
>>>
>>> Or do you prefer only receiving the patches, and not the emails with the
>>> reasons not to backport some of them?
>>>
>>> About the patches, do you prefer to receive one big series per version
>>> or individual patches sent in reply to the different 'FAILED: patch'
>>> emails like I did?
>>
>> One big series, per kernel tree, would be ideal as that way I don't have
>> to pick them out and guess as to the order.
>
>Sure, I will do that next time, it is even easier for me.
>
>I sent the patches in the same order as they are in my working branch,
>but I understand they could be received in a different order.
>
>> Also, if you don't respond to the FAILED emails, that's fine with me, I
>> don't keep track, but maybe Sasha does as I know he does backports based
>> on them at times.  So I'll let him answer that.
>
>Thanks! I will wait for Sasha's reply.

Doesn't matter on my end :)

-- 
Thanks,
Sasha

      reply	other threads:[~2024-09-07 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  9:36 MPTCP stable backports: is the workflow OK? Matthieu Baerts
2024-09-06  9:56 ` Greg KH
2024-09-06 10:10   ` Matthieu Baerts
2024-09-07 15:43     ` Sasha Levin [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=Ztx0ii15ulDATpUK@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --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