From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>,
Daniel Wagner <dwagner@suse.de>,
John Garry <john.g.garry@oracle.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v4 0/2] nvme-multipath: expose path_state via sysfs
Date: Fri, 18 Sep 2026 15:25:55 +0200 [thread overview]
Message-ID: <20260918132555.GA17993@lst.de> (raw)
In-Reply-To: <097fa1af-41eb-461b-873e-b5f27e1ae872@linux.alibaba.com>
On Mon, Sep 07, 2026 at 10:15:24AM +0800, Guixin Liu wrote:
> Hi, any comments here?
Looks good to me. I'd probably merge both patches into one, though.
next prev parent reply other threads:[~2026-09-18 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:00 [PATCH v4 0/2] nvme-multipath: expose path_state via sysfs Guixin Liu
2026-07-24 9:00 ` [PATCH v4 1/2] " Guixin Liu
2026-07-24 9:00 ` [PATCH v4 2/2] nvme-multipath: document path_state sysfs attribute Guixin Liu
2026-08-05 1:55 ` [PATCH v4 0/2] nvme-multipath: expose path_state via sysfs Guixin Liu
2026-09-07 2:15 ` Guixin Liu
2026-09-18 13:25 ` Christoph Hellwig [this message]
2026-09-20 2:07 ` 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=20260918132555.GA17993@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=john.g.garry@oracle.com \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.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