From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, quic_hardshar@quicinc.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce()
Date: Fri, 25 Jul 2025 20:25:12 -0400 [thread overview]
Message-ID: <1753460458-7d532680@stable.kernel.org> (raw)
In-Reply-To: <20250725112710.219313-1-quic_hardshar@quicinc.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Could not find matching upstream commit
No upstream commit was identified. Using temporary commit for testing.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 6.6 | Success | Success |
next prev parent reply other threads:[~2025-07-26 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 11:27 [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce() Hardeep Sharma
2025-07-25 12:04 ` Greg KH
2025-07-26 0:25 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-14 6:36 Hardeep Sharma
2025-08-14 9:03 ` Greg KH
2025-08-14 10:54 ` Hardeep Sharma
2025-08-14 11:36 ` Greg KH
2025-08-14 13:06 ` Hardeep Sharma
2025-08-14 13:54 ` Greg KH
2025-08-14 13:11 ` Hardeep Sharma
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=1753460458-7d532680@stable.kernel.org \
--to=sashal@kernel.org \
--cc=quic_hardshar@quicinc.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