From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Devaansh Kumar <devaanshk840@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] bpf: Remove tracing program restriction on map types
Date: Tue, 15 Apr 2025 17:43:51 -0400 [thread overview]
Message-ID: <20250415111814-87ab1240b7637bc3@stable.kernel.org> (raw)
In-Reply-To: <20250415130910.2326537-1-devaanshk840@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 96da3f7d489d11b43e7c1af90d876b9a2492cca8
WARNING: Author mismatch between patch and upstream commit:
Backport author: Devaansh Kumar<devaanshk840@gmail.com>
Commit author: Alexei Starovoitov<ast@kernel.org>
Note: The patch differs from the upstream commit:
---
1: 96da3f7d489d1 < -: ------------- bpf: Remove tracing program restriction on map types
-: ------------- > 1: 9bc5c94e278f7 Linux 6.14.2
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
| stable/linux-6.13.y | Success | Success |
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
prev parent reply other threads:[~2025-04-15 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:09 [PATCH] bpf: Remove tracing program restriction on map types Devaansh Kumar
2025-04-15 13:19 ` Greg KH
2025-04-15 13:25 ` Devaansh Kumar
2025-04-15 15:01 ` Alexei Starovoitov
2025-04-15 21: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=20250415111814-87ab1240b7637bc3@stable.kernel.org \
--to=sashal@kernel.org \
--cc=devaanshk840@gmail.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