linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] block: Add bio_max_segs
Date: Fri, 26 Feb 2021 15:50:35 -0700	[thread overview]
Message-ID: <307e1cef-0932-b7f2-4d65-42983e3e0d1b@kernel.dk> (raw)
In-Reply-To: <20210226203819.GH2723601@casper.infradead.org>

On 2/26/21 1:38 PM, Matthew Wilcox wrote:
> 
> This seems to have missed the merge window ;-(

It ain't over yet, and I haven't shipped my final bits for 5.12 for
block yet... I'll queue it up.

-- 
Jens Axboe


      parent reply	other threads:[~2021-02-26 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  4:38 [PATCH v2] block: Add bio_max_segs Matthew Wilcox (Oracle)
2021-02-26 20:38 ` Matthew Wilcox
2021-02-26 20:50   ` Chaitanya Kulkarni
2021-02-26 22:50   ` 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=307e1cef-0932-b7f2-4d65-42983e3e0d1b@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).