From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.g.garry@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] block: remove the ioprio field from struct request
Date: Wed, 13 Nov 2024 06:06:16 +0100 [thread overview]
Message-ID: <20241113050616.GA20749@lst.de> (raw)
In-Reply-To: <b7746182-f2d4-4cb0-8028-93e405b1c4ec@oracle.com>
On Tue, Nov 12, 2024 at 06:22:24PM +0000, John Garry wrote:
> And at many points bio->bi_ioprio is written without using bio_set_prio(),
> so I doubt the use of that one as well..
>
> I do realize that all this is outside the scope of this series.
Agreed to all of the above. If anyone is in for an easy cleanup, go
for it!
next prev parent reply other threads:[~2024-11-13 5:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241112183746epcas5p40dcbbbd42a0f0be597193bf0808f8e67@epcas5p4.samsung.com>
2024-11-12 17:00 ` remove two fields from struct request Christoph Hellwig
2024-11-12 17:00 ` [PATCH 1/2] block: remove the write_hint field " Christoph Hellwig
2024-11-12 18:29 ` Bart Van Assche
2024-11-12 18:32 ` Bart Van Assche
2024-11-12 17:00 ` [PATCH 2/2] block: remove the ioprio " Christoph Hellwig
2024-11-12 18:22 ` John Garry
2024-11-13 5:06 ` Christoph Hellwig [this message]
2024-11-12 18:32 ` Bart Van Assche
2024-11-22 5:04 ` Sam Protsenko
2024-11-22 12:04 ` Christoph Hellwig
2024-11-22 21:55 ` Sam Protsenko
2024-11-22 22:18 ` Bart Van Assche
2024-11-25 23:13 ` Sam Protsenko
2024-11-25 7:36 ` Christoph Hellwig
2024-11-26 1:37 ` Sam Protsenko
2024-11-26 6:52 ` Christoph Hellwig
2024-11-26 7:37 ` Sam Protsenko
2024-11-12 18:29 ` remove two fields " Nitesh Shetty
2024-11-12 21:43 ` 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=20241113050616.GA20749@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.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