From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.15.y 2/3] selftests: mptcp: connect: also cover alt modes
Date: Wed, 30 Jul 2025 21:09:38 -0400 [thread overview]
Message-ID: <aIrCUht5H3ALyGsu@lappy> (raw)
In-Reply-To: <bf0ed59b-c519-4aa1-b05e-160dac6b5b8f@kernel.org>
On Wed, Jul 30, 2025 at 06:41:19PM +0200, Matthieu Baerts wrote:
>Hi Sasha,
>
>On 30/07/2025 18:28, Sasha Levin wrote:
>> [ Sasha's backport helper bot ]
>>
>> Hi,
>>
>> Summary of potential issues:
>> ℹ️ This is part 2/3 of a series
>> ⚠️ Could not find matching upstream commit
>>
>> The claimed upstream commit SHA1 (37848a456fc38c191aedfe41f662cc24db8c23d9) was not found.
>
>Is there maybe an issue with your bot? The SHA1 looks correct:
>
>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37848a456fc38c191aedfe41f662cc24db8c23d9
>
>Also the same as the one mentioned in Greg's email:
>
> https://lore.kernel.org/2025072839-wildly-gala-e85f@gregkh
The SHA1 is correct, but it wasn't in Linus's tree until earlier today
via 8be4d31cb8aa ("Merge tag 'net-next-6.17' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next").
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-07-31 1:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 13:48 FAILED: patch "[PATCH] selftests: mptcp: connect: also cover alt modes" failed to apply to 5.15-stable tree gregkh
2025-07-29 14:20 ` [PATCH 5.15.y] selftests: mptcp: connect: also cover alt modes Sasha Levin
2025-07-29 14:32 ` Matthieu Baerts
2025-07-29 14:36 ` Sasha Levin
2025-07-30 10:28 ` [PATCH 5.15.y 0/3] mptcp: fix recent failed backports (20250728) Matthieu Baerts (NGI0)
2025-07-30 10:28 ` [PATCH 5.15.y 1/3] selftests: mptcp: make sendfile selftest work Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
2025-08-22 13:44 ` Patch "selftests: mptcp: make sendfile selftest work" has been added to the 5.15-stable tree gregkh
2025-07-30 10:28 ` [PATCH 5.15.y 2/3] selftests: mptcp: connect: also cover alt modes Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
2025-07-30 16:41 ` Matthieu Baerts
2025-07-31 1:09 ` Sasha Levin [this message]
2025-07-31 9:28 ` Matthieu Baerts
2025-08-22 13:44 ` Patch "selftests: mptcp: connect: also cover alt modes" has been added to the 5.15-stable tree gregkh
2025-07-30 10:28 ` [PATCH 5.15.y 3/3] selftests: mptcp: connect: also cover checksum Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
2025-08-22 13:44 ` Patch "selftests: mptcp: connect: also cover checksum" has been added to the 5.15-stable tree gregkh
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=aIrCUht5H3ALyGsu@lappy \
--to=sashal@kernel.org \
--cc=matttbe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.