From: Christoph Hellwig <hch@lst.de>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
sagi@grimberg.me, emilne@redhat.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
jrani@purestorage.com, randyj@purestorage.com, hare@kernel.org
Subject: Re: [PATCH v5] nvme: multipath: Implemented new iopolicy "queue-depth"
Date: Thu, 23 May 2024 15:16:17 +0200 [thread overview]
Message-ID: <20240523131617.GA23604@lst.de> (raw)
In-Reply-To: <fe13bd05-76c5-4bf8-bfda-f9ecf08b2272@redhat.com>
On Thu, May 23, 2024 at 09:12:21AM -0400, John Meneghini wrote:
> On 5/23/24 02:45, Christoph Hellwig wrote:> On Wed, May 22, 2024 at 11:32:02AM -0600, Keith Busch wrote:
>>> Christoph, Sagi, 6.10 merge window is still open and this has been
>>> iterating long before that. Any objection?
>>
>> No, it's not. The window for development closes with the release for
>> 6.9. New features must be in before that.
>
> So what's the next window for new features? 6.11?
What else?
next prev parent reply other threads:[~2024-05-23 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 16:54 [PATCH v5] nvme: multipath: Implemented new iopolicy "queue-depth" John Meneghini
2024-05-22 17:32 ` Keith Busch
2024-05-23 6:45 ` Christoph Hellwig
2024-05-23 13:12 ` John Meneghini
2024-05-23 13:16 ` Christoph Hellwig [this message]
2024-05-23 13:33 ` John Meneghini
2024-05-23 15:56 ` Keith Busch
2024-05-23 3:00 ` John Meneghini
2024-05-23 4:29 ` Chaitanya Kulkarni
2024-05-23 6:28 ` Hannes Reinecke
2024-05-23 13:42 ` John Meneghini
2024-05-23 19:33 ` Chaitanya Kulkarni
2024-05-23 19:28 ` Chaitanya Kulkarni
2024-05-23 6:52 ` Christoph Hellwig
2024-05-23 15:08 ` John Meneghini
2024-05-23 8:14 ` Christoph Hellwig
2024-05-23 16:07 ` John Meneghini
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=20240523131617.GA23604@lst.de \
--to=hch@lst.de \
--cc=emilne@redhat.com \
--cc=hare@kernel.org \
--cc=jmeneghi@redhat.com \
--cc=jrani@purestorage.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=randyj@purestorage.com \
--cc=sagi@grimberg.me \
/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