From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] net/mlx5e: Don't call cleanup on profile rollback failure
Date: Thu, 26 Dec 2024 11:44:29 -0500 [thread overview]
Message-ID: <20241226094137-4aaef6d305ca4ea6@stable.kernel.org> (raw)
In-Reply-To: <20241226071131.773866-1-jianqi.ren.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 4dbc1d1a9f39c3711ad2a40addca04d07d9ab5d0
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Cosmin Ratiu <cratiu@nvidia.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 4dbc1d1a9f39 < -: ------------ net/mlx5e: Don't call cleanup on profile rollback failure
-: ------------ > 1: 4defc045120c net/mlx5e: Don't call cleanup on profile rollback failure
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-26 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 7:11 [PATCH 6.1.y] net/mlx5e: Don't call cleanup on profile rollback failure jianqi.ren.cn
2024-12-26 16:44 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 10:09 jianqi.ren.cn
2024-12-11 9:18 ` Greg KH
2024-12-11 16:33 ` Sasha Levin
2024-12-10 6:55 jianqi.ren.cn
2024-12-10 19:25 ` Sasha Levin
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=20241226094137-4aaef6d305ca4ea6@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@windriver.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