From: Jens Axboe <axboe@kernel.dk>
To: Coly Li <i@coly.li>
Cc: linux-block@vger.kernel.org, Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: Fwd: [PATCH] badblocks: Fix a nonsense WARN_ON() which checks whether a u64 variable < 0
Date: Mon, 10 Mar 2025 07:42:54 -0600 [thread overview]
Message-ID: <de3a5313-b0b5-432f-ace2-f6859eeb4436@kernel.dk> (raw)
In-Reply-To: <18D3673D-575E-4002-B5A8-FEE56A732EDC@coly.li>
On 3/9/25 10:12 AM, Coly Li wrote:
> Hi Jens,
>
> Could you please take a look at it and pick this patch into the for-6.15/block branch? The patch is generated based on the for-6.15/block branch.
Just a heads-up - you don't need to send these emails outside of
just sending the patch, I do get the patches. If I didn't, then that'd
be a problem. If you feel patches need extra context, then just do a
cover letter for them.
--
Jens Axboe
next prev parent reply other threads:[~2025-03-10 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 16:05 [PATCH] badblocks: Fix a nonsense WARN_ON() which checks whether a u64 variable < 0 colyli
2025-03-09 16:12 ` Fwd: " Coly Li
2025-03-10 13:42 ` Jens Axboe [this message]
2025-03-10 13:44 ` Coly Li
2025-03-10 13:49 ` Jens Axboe
2025-03-10 13:50 ` Coly Li
2025-03-10 2:06 ` Yu Kuai
2025-03-10 13:50 ` Jens Axboe
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=de3a5313-b0b5-432f-ace2-f6859eeb4436@kernel.dk \
--to=axboe@kernel.dk \
--cc=dan.carpenter@linaro.org \
--cc=i@coly.li \
--cc=linux-block@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