From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Cc: Ming Lei <ming.lei@redhat.com>, Omar Sandoval <osandov@fb.com>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumanesh Samanta <sumanesh.samanta@broadcom.com>,
"Ewan D . Milne" <emilne@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH V5 01/13] sbitmap: remove sbitmap_clear_bit_unlock
Date: Thu, 19 Nov 2020 17:33:50 +0800 [thread overview]
Message-ID: <20201119093402.279318-2-ming.lei@redhat.com> (raw)
In-Reply-To: <20201119093402.279318-1-ming.lei@redhat.com>
No one uses this helper any more, so kill it.
Cc: Omar Sandoval <osandov@fb.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Sumanesh Samanta <sumanesh.samanta@broadcom.com>
Cc: Ewan D. Milne <emilne@redhat.com>
Cc: Hannes Reinecke <hare@suse.de>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Tested-by: Sumanesh Samanta <sumanesh.samanta@broadcom.com>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
---
include/linux/sbitmap.h | 6 ------
1 file changed, 6 deletions(-)
diff --git a/include/linux/sbitmap.h b/include/linux/sbitmap.h
index e40d019c3d9d..51edc05489cb 100644
--- a/include/linux/sbitmap.h
+++ b/include/linux/sbitmap.h
@@ -320,12 +320,6 @@ static inline void sbitmap_deferred_clear_bit(struct sbitmap *sb, unsigned int b
set_bit(SB_NR_TO_BIT(sb, bitnr), addr);
}
-static inline void sbitmap_clear_bit_unlock(struct sbitmap *sb,
- unsigned int bitnr)
-{
- clear_bit_unlock(SB_NR_TO_BIT(sb, bitnr), __sbitmap_word(sb, bitnr));
-}
-
static inline int sbitmap_test_bit(struct sbitmap *sb, unsigned int bitnr)
{
return test_bit(SB_NR_TO_BIT(sb, bitnr), __sbitmap_word(sb, bitnr));
--
2.25.4
next prev parent reply other threads:[~2020-11-19 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:33 [PATCH V5 00/13] blk-mq/scsi: tracking device queue depth via sbitmap Ming Lei
2020-11-19 9:33 ` Ming Lei [this message]
2020-11-19 9:33 ` [PATCH V5 02/13] sbitmap: maintain allocation round_robin in sbitmap Ming Lei
2020-11-19 9:33 ` [PATCH V5 03/13] sbitmap: add helpers for updating allocation hint Ming Lei
2020-11-19 9:33 ` [PATCH V5 04/13] sbitmap: move allocation hint into sbitmap Ming Lei
2020-11-19 9:33 ` [PATCH V5 05/13] sbitmap: export sbitmap_weight Ming Lei
2020-11-19 9:33 ` [PATCH V5 06/13] sbitmap: add helper of sbitmap_calculate_shift Ming Lei
2020-11-19 9:33 ` [PATCH V5 07/13] blk-mq: add callbacks for storing & retrieving budget token Ming Lei
2020-11-19 9:33 ` [PATCH V5 08/13] blk-mq: return budget token from .get_budget callback Ming Lei
2020-11-19 9:33 ` [PATCH V5 09/13] scsi: put hot fields of scsi_host_template into one cacheline Ming Lei
2020-11-19 9:42 ` [PATCH V5 00/13] blk-mq/scsi: tracking device queue depth via sbitmap Ming Lei
2020-11-19 9:46 Ming Lei
2020-11-19 9:46 ` [PATCH V5 01/13] sbitmap: remove sbitmap_clear_bit_unlock Ming Lei
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=20201119093402.279318-2-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=johannes.thumshirn@wdc.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=osandov@fb.com \
--cc=sumanesh.samanta@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.