From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10] dma-buf: insert memory barrier before updating num_fences
Date: Sat, 9 Aug 2025 19:40:59 -0400 [thread overview]
Message-ID: <1754749472-e511209e@stable.kernel.org> (raw)
In-Reply-To: <20250808180537.26649-1-wanjay@amazon.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: 72c7d62583ebce7baeb61acce6057c361f73be4a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Jay Wang <wanjay@amazon.com>
Commit author: Hyejeong Choi <hjeong.choi@samsung.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (different SHA1: fe1bebd0edb2)
6.6.y | Present (different SHA1: c9d2b9a80d06)
6.1.y | Present (different SHA1: 3becc659f9cb)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 72c7d62583eb < -: ------------ dma-buf: insert memory barrier before updating num_fences
-: ------------ > 1: eb3b4ab80d5e dma-buf: insert memory barrier before updating num_fences
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-08-09 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 18:05 [PATCH 5.10] dma-buf: insert memory barrier before updating num_fences Jay Wang
2025-08-09 23:40 ` 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=1754749472-e511209e@stable.kernel.org \
--to=sashal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox