From: Omar Sandoval <osandov@osandov.com>
To: Shenghui Wang <shhuiw@foxmail.com>
Cc: axboe@kernel.dk, osandov@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sbitmap: trivial - update comment for sbitmap_deferred_clear_bit
Date: Thu, 21 Mar 2019 15:12:26 -0700 [thread overview]
Message-ID: <20190321221226.GC20838@vader> (raw)
In-Reply-To: <20190316082437.2766-1-shhuiw@foxmail.com>
On Sat, Mar 16, 2019 at 04:24:37PM +0800, Shenghui Wang wrote:
> "sbitmap_batch_clear" should be "sbitmap_deferred_clear"
Acked-by: Omar Sandoval <osandov@fb.com>
> Signed-off-by: Shenghui Wang <shhuiw@foxmail.com>
> ---
> include/linux/sbitmap.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/sbitmap.h b/include/linux/sbitmap.h
> index 14d558146aea..20f3e3f029b9 100644
> --- a/include/linux/sbitmap.h
> +++ b/include/linux/sbitmap.h
> @@ -330,7 +330,7 @@ static inline void sbitmap_clear_bit(struct sbitmap *sb, unsigned int bitnr)
> /*
> * This one is special, since it doesn't actually clear the bit, rather it
> * sets the corresponding bit in the ->cleared mask instead. Paired with
> - * the caller doing sbitmap_batch_clear() if a given index is full, which
> + * the caller doing sbitmap_deferred_clear() if a given index is full, which
> * will clear the previously freed entries in the corresponding ->word.
> */
> static inline void sbitmap_deferred_clear_bit(struct sbitmap *sb, unsigned int bitnr)
> --
> 2.20.1
>
>
>
next prev parent reply other threads:[~2019-03-21 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 8:24 [PATCH] sbitmap: trivial - update comment for sbitmap_deferred_clear_bit Shenghui Wang
2019-03-21 22:12 ` Omar Sandoval [this message]
2019-03-22 17:01 ` 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=20190321221226.GC20838@vader \
--to=osandov@osandov.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=shhuiw@foxmail.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).