From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: lanbincn@qq.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] RDMA/rxe: Fix the qp flush warnings in req
Date: Tue, 14 Jan 2025 07:43:54 -0500 [thread overview]
Message-ID: <20250114073101-d2f9eb44d297de58@stable.kernel.org> (raw)
In-Reply-To: <tencent_92588BE248C1F834ECD126D5EC7E0048320A@qq.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: ea4c990fa9e19ffef0648e40c566b94ba5ab31be
WARNING: Author mismatch between patch and upstream commit:
Backport author: lanbincn@qq.com
Commit author: Zhu Yanjun<yanjun.zhu@linux.dev>
Status in newer kernel trees:
6.12.y | Present (different SHA1: cc341b5d761a)
6.6.y | Present (different SHA1: 31978d5c5aef)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: ea4c990fa9e1 < -: ------------ RDMA/rxe: Fix the qp flush warnings in req
-: ------------ > 1: cd4186530dfd RDMA/rxe: Fix the qp flush warnings in req
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-01-14 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 3:48 [PATCH 6.1.y] RDMA/rxe: Fix the qp flush warnings in req lanbincn
2025-01-14 12: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=20250114073101-d2f9eb44d297de58@stable.kernel.org \
--to=sashal@kernel.org \
--cc=lanbincn@qq.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