From: Christoph Hellwig <hch@lst.de>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 4/8] nvmet: Make nvmet_debugfs static
Date: Thu, 22 Aug 2024 08:57:54 +0200 [thread overview]
Message-ID: <20240822065754.GD3141@lst.de> (raw)
In-Reply-To: <20240819120020.3884893-1-ruanjinjie@huawei.com>
The change looks good to me, but given that you sent a series where
I can't see the other patches I have no idea what context this needs.
If this is a standalone patch, please resend it standalone, if not
make sure every recipient is Cced for every patch.
prev parent reply other threads:[~2024-08-22 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 12:00 [PATCH -next 4/8] nvmet: Make nvmet_debugfs static Jinjie Ruan
2024-08-22 6:57 ` Christoph Hellwig [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=20240822065754.GD3141@lst.de \
--to=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ruanjinjie@huawei.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 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.