From: Christoph Hellwig <hch@lst.de>
To: Julian Sun <sunjunchao@bytedance.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, sagi@grimberg.me, kch@nvidia.com,
armenx.baloyan@intel.com, james.p.freyensee@intel.com,
ming.l@ssi.samsung.com, Runyu Xiao <runyu.xiao@seu.edu.cn>
Subject: Re: [PATCH 1/2] nvmet: preserve device path on allocation failure.
Date: Thu, 10 Sep 2026 07:37:12 +0200 [thread overview]
Message-ID: <20260910053712.GA27511@lst.de> (raw)
In-Reply-To: <72eecee9-c103-4c6b-adc8-0fa1367313f3@bytedance.com>
On Thu, Sep 10, 2026 at 01:35:10PM +0800, Julian Sun wrote:
> On 9/10/26 1:25 PM, Christoph Hellwig wrote:
>> Can you coordinate this with the configfs path checking series
>> from Runyu Xiao? That one had a few resends, so I'd like to get it in
>> first.
>
> Sure, I'll rebase and resend once you've merged Runyu's patches.
Actually I noticed we need another respin of that anyway. Let me review
your patches and see if we can fast track them in.
next prev parent reply other threads:[~2026-09-10 5:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 3:35 [PATCH 1/2] nvmet: preserve device path on allocation failure Julian Sun
2026-09-08 3:35 ` [PATCH 2/2] nvmet: reject enabling a namespace without a device path Julian Sun
2026-09-10 5:42 ` Christoph Hellwig
2026-09-10 5:47 ` Julian Sun
2026-09-10 5:25 ` [PATCH 1/2] nvmet: preserve device path on allocation failure Christoph Hellwig
2026-09-10 5:35 ` Julian Sun
2026-09-10 5:37 ` Christoph Hellwig [this message]
2026-09-10 5:42 ` Christoph Hellwig
2026-09-11 14:45 ` Keith Busch
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=20260910053712.GA27511@lst.de \
--to=hch@lst.de \
--cc=armenx.baloyan@intel.com \
--cc=james.p.freyensee@intel.com \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.l@ssi.samsung.com \
--cc=runyu.xiao@seu.edu.cn \
--cc=sagi@grimberg.me \
--cc=sunjunchao@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.