From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: John Garry <john.g.garry@oracle.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "haris.iqbal@ionos.com" <haris.iqbal@ionos.com>,
"jinpu.wang@ionos.com" <jinpu.wang@ionos.com>,
"colyli@suse.de" <colyli@suse.de>,
"kent.overstreet@linux.dev" <kent.overstreet@linux.dev>,
"agk@redhat.com" <agk@redhat.com>,
"snitzer@kernel.org" <snitzer@kernel.org>,
"mpatocka@redhat.com" <mpatocka@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
"dm-devel@lists.linux.dev" <dm-devel@lists.linux.dev>,
"linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH 0/2] block: Delete bio_set_prio() and bio_prio()
Date: Tue, 3 Dec 2024 02:10:31 +0000 [thread overview]
Message-ID: <14da2382-5523-4207-90e0-ddef7c69e496@nvidia.com> (raw)
In-Reply-To: <20241202111957.2311683-1-john.g.garry@oracle.com>
On 12/2/24 03:19, John Garry wrote:
> 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.
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-12-03 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:19 [PATCH 0/2] block: Delete bio_set_prio() and bio_prio() John Garry
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 ` Chaitanya Kulkarni [this message]
2024-12-03 13:42 ` [PATCH 0/2] block: Delete bio_set_prio() and bio_prio() 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=14da2382-5523-4207-90e0-ddef7c69e496@nvidia.com \
--to=chaitanyak@nvidia.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=john.g.garry@oracle.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