From: Jens Axboe <axboe@kernel.dk>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH 0/1] cdrom: patch for inclusion in 6.10
Date: Wed, 15 May 2024 13:00:06 -0600 [thread overview]
Message-ID: <171579960632.171640.15923003704981684226.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240507222520.1445-1-phil@philpotter.co.uk>
On Tue, 07 May 2024 23:25:19 +0100, Phillip Potter wrote:
> Please apply the following patch to your for-6.10/block tree from
> Justin Stitt, that changes a media change condition in a sensible
> way to not require a subtraction anymore, thus no longer triggering
> the re-enabled signed integer overflow sanitizer in Clang/UBSan.
>
> Many thanks in advance.
>
> [...]
Applied, thanks!
[1/1] cdrom: rearrange last_media_change check to avoid unintentional overflow
commit: efb905aeb44b0e99c0e6b07865b1885ae0471ebf
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-05-15 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 22:25 [PATCH 0/1] cdrom: patch for inclusion in 6.10 Phillip Potter
2024-05-07 22:25 ` [PATCH 1/1] cdrom: rearrange last_media_change check to avoid unintentional overflow Phillip Potter
2024-05-15 19:00 ` Jens Axboe [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=171579960632.171640.15923003704981684226.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=phil@philpotter.co.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).