public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, shung-hsi.yu@suse.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 6.6 6.12 1/1] selftests/bpf: Check for timeout in perf_link test
Date: Wed, 11 Jun 2025 09:16:09 -0400	[thread overview]
Message-ID: <20250610150600-484b48f7ef1ad86d@stable.kernel.org> (raw)
In-Reply-To: <20250609052941.52073-1-shung-hsi.yu@suse.com>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it

Found matching upstream commit: e6c209da7e0e9aaf955a7b59e91ed78c2b6c96fb

WARNING: Author mismatch between patch and found commit:
Backport author: Shung-Hsi Yu<shung-hsi.yu@suse.com>
Commit author: Ihor Solodrai<ihor.solodrai@pm.me>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.y | Present (exact SHA1)
6.12.y | Not found

Note: The patch differs from the upstream commit:
---
1:  e6c209da7e0e9 ! 1:  8249587f33f76 selftests/bpf: Check for timeout in perf_link test
    @@ Commit message
         Signed-off-by: Ihor Solodrai <ihor.solodrai@pm.me>
         Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
         Link: https://lore.kernel.org/bpf/20241011153104.249800-1-ihor.solodrai@pm.me
    +    Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
     
      ## tools/testing/selftests/bpf/prog_tests/perf_link.c ##
     @@
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y       |  Success    |  Success   |

  reply	other threads:[~2025-06-11 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09  5:29 [PATCH stable 6.6 6.12 1/1] selftests/bpf: Check for timeout in perf_link test Shung-Hsi Yu
2025-06-11 13:16 ` Sasha Levin [this message]
2025-06-20 15:52 ` Greg KH

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=20250610150600-484b48f7ef1ad86d@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=shung-hsi.yu@suse.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