From: Jens Axboe <axboe@kernel.dk>
To: Shaohua Li <shli@fb.com>,
linux-raid@vger.kernel.org, linux-block@vger.kernel.org
Cc: tomasz.majchrzak@intel.com
Subject: Re: [PATCH] badblocks: badblocks_set/clear update unacked_exist
Date: Fri, 21 Oct 2016 10:15:28 -0600 [thread overview]
Message-ID: <ef73bc09-433d-8c3b-d70f-3400d4624ed5@kernel.dk> (raw)
In-Reply-To: <39f303dcb7bdf2958b6f82a0646467dfbc8d1abd.1476999400.git.shli@fb.com>
On 10/20/2016 03:40 PM, Shaohua Li wrote:
> When bandblocks_set acknowledges a range or badblocks_clear a range,
> it's possible all badblocks are acknowledged. We should update
> unacked_exist if this occurs.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2016-10-21 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 21:40 [PATCH] badblocks: badblocks_set/clear update unacked_exist Shaohua Li
2016-10-21 14:35 ` Tomasz Majchrzak
2016-10-21 16:15 ` 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=ef73bc09-433d-8c3b-d70f-3400d4624ed5@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.com \
--cc=tomasz.majchrzak@intel.com \
/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 NNTP newsgroup(s).