Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: John Garry <john.g.garry@oracle.com>, linux-nvme@lists.infradead.org
Cc: hare@suse.de, kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
	dwagner@suse.de, kanie@linux.alibaba.com, jmeneghi@redhat.com,
	randyj@purestorage.com, martin.petersen@oracle.com,
	gjoyce@linux.ibm.com
Subject: Re: [PATCH v7 0/9] nvme-multipath: introduce latency I/O policy
Date: Mon, 10 Aug 2026 22:57:26 +0530	[thread overview]
Message-ID: <e229a15e-26d1-44e6-8cb6-fa59255d609e@linux.ibm.com> (raw)
In-Reply-To: <35c99788-ad97-420d-b16d-5ba8f6a28f82@oracle.com>

On 8/10/26 1:20 PM, John Garry wrote:
> This does not apply (cleanly) to the nvme-7.3 branch. It applies to v7.2-rc7. I would think that it should apply to the nvme-7.3 branch. Or am I missing something?

Yes, you're right. It should have been rebased onto the current nvme-7.3 branch.
I'll rebase it and send the updated version in the next revision.

Thanks,
--Nilay


  reply	other threads:[~2026-08-10 17:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 10:07 [PATCH v7 0/9] nvme-multipath: introduce latency I/O policy Nilay Shroff
2026-08-09 10:07 ` [PATCH v7 1/9] block: expose blk_stat_{enable,disable}_accounting() to drivers Nilay Shroff
2026-08-10  8:18   ` John Garry
2026-08-09 10:07 ` [PATCH v7 2/9] block: record I/O request start time for passthru request Nilay Shroff
2026-08-10  6:44   ` Hannes Reinecke
2026-08-09 10:07 ` [PATCH v7 3/9] nvme-multipath: pass I/O type to nvme_find_path() Nilay Shroff
2026-08-10  8:57   ` John Garry
2026-08-10 17:19     ` Nilay Shroff
2026-08-11 10:36       ` John Garry
2026-08-12  8:05         ` Nilay Shroff
2026-08-09 10:07 ` [PATCH v7 4/9] nvme-multipath: add support for latency I/O policy Nilay Shroff
2026-08-10  8:12   ` John Garry
2026-08-10 17:25     ` Nilay Shroff
2026-08-11 10:26       ` John Garry
2026-08-12  8:01         ` Nilay Shroff
2026-08-10 10:46   ` John Garry
2026-08-10 15:25     ` Nilay Shroff
2026-08-11 10:03       ` John Garry
2026-08-12  7:55         ` Nilay Shroff
2026-08-09 10:08 ` [PATCH v7 5/9] nvme: add generic debugfs support Nilay Shroff
2026-08-09 10:08 ` [PATCH v7 6/9] nvme-multipath: add debugfs attribute latency_ewma_shift Nilay Shroff
2026-08-09 10:08 ` [PATCH v7 7/9] nvme-multipath: add debugfs attribute latency_batch_timeout Nilay Shroff
2026-08-09 10:08 ` [PATCH v7 8/9] nvme-multipath: add debugfs attribute latency_stat Nilay Shroff
2026-08-09 10:08 ` [PATCH v7 9/9] nvme-multipath: add documentation for latency I/O policy Nilay Shroff
2026-08-10  6:45   ` Hannes Reinecke
2026-08-10  7:50 ` [PATCH v7 0/9] nvme-multipath: introduce " John Garry
2026-08-10 17:27   ` Nilay Shroff [this message]
2026-08-11  9:37     ` John Garry
2026-08-12  8:07       ` Nilay Shroff
2026-08-10  9:43 ` Guixin Liu

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=e229a15e-26d1-44e6-8cb6-fa59255d609e@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=dwagner@suse.de \
    --cc=gjoyce@linux.ibm.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=john.g.garry@oracle.com \
    --cc=kanie@linux.alibaba.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --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