From: John Garry <john.g.garry@oracle.com>
To: axboe@kernel.dk
Cc: haris.iqbal@ionos.com, jinpu.wang@ionos.com, colyli@suse.de,
kent.overstreet@linux.dev, agk@redhat.com, snitzer@kernel.org,
mpatocka@redhat.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org,
dm-devel@lists.linux.dev, linux-bcachefs@vger.kernel.org,
hch@lst.de, John Garry <john.g.garry@oracle.com>
Subject: [PATCH 0/2] block: Delete bio_set_prio() and bio_prio()
Date: Mon, 2 Dec 2024 11:19:55 +0000 [thread overview]
Message-ID: <20241202111957.2311683-1-john.g.garry@oracle.com> (raw)
Macros bio_set_prio() and bio_prio() do nothing special in terms of
setting and getting the bio io prio member, so just delete them.
Prior to commit 43b62ce3ff0a, they would actually encode and decode the
prio in the now-deleted bi_rw member.
John Garry (2):
block: Delete bio_prio()
block: Delete bio_set_prio()
drivers/block/rnbd/rnbd-srv.c | 2 +-
drivers/md/bcache/movinggc.c | 2 +-
drivers/md/bcache/writeback.c | 2 +-
drivers/md/dm-verity-fec.c | 6 +++---
drivers/md/dm-verity-target.c | 4 ++--
fs/bcachefs/move.c | 6 +++---
include/linux/bio.h | 3 ---
7 files changed, 11 insertions(+), 14 deletions(-)
--
2.31.1
next reply other threads:[~2024-12-02 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:19 John Garry [this message]
2024-12-02 11:19 ` [PATCH 1/2] block: Delete bio_prio() John Garry
2024-12-02 11:19 ` [PATCH 2/2] block: Delete bio_set_prio() John Garry
2024-12-02 11:33 ` Jinpu Wang
2024-12-02 16:21 ` Coly Li
2024-12-03 2:10 ` [PATCH 0/2] block: Delete bio_set_prio() and bio_prio() Chaitanya Kulkarni
2024-12-03 13:42 ` 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=20241202111957.2311683-1-john.g.garry@oracle.com \
--to=john.g.garry@oracle.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dm-devel@lists.linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=hch@lst.de \
--cc=jinpu.wang@ionos.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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
all inboxes | Powered by JetHome®