public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: rename BIO_MAX_PAGES
Date: Thu, 11 Mar 2021 07:48:17 -0700	[thread overview]
Message-ID: <45639533-59bd-3634-b8ba-6dea07417384@kernel.dk> (raw)
In-Reply-To: <20210311110137.1132391-1-hch@lst.de>

On 3/11/21 4:01 AM, Christoph Hellwig wrote:
> Hi Jens,
> 
> this patch renames BIO_MAX_PAGES to BIO_MAX_VECS as the old name
> has been utterly wrong for a while now.  It might be a good idea
> to get this to Linus before -rc3 to minimize any merge conflicts.

Sure, better now than carry it for the next merge window and deal
with that...

-- 
Jens Axboe


      parent reply	other threads:[~2021-03-11 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 11:01 rename BIO_MAX_PAGES Christoph Hellwig
2021-03-11 11:01 ` [PATCH] block: rename BIO_MAX_PAGES to BIO_MAX_VECS Christoph Hellwig
2021-03-11 12:11   ` Matthew Wilcox
2021-03-11 14:28   ` Martin K. Petersen
2021-03-11 15:00   ` Ming Lei
2021-03-11 14:48 ` Jens Axboe [this message]

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=45639533-59bd-3634-b8ba-6dea07417384@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@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