From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC
Date: Sat, 25 Apr 2026 22:16:11 +0900 [thread overview]
Message-ID: <9d96e920-e52c-4946-ba40-332bae38d7db@gmail.com> (raw)
In-Reply-To: <aetx7GZeKBoRCPS3@infradead.org>
On 2026/04/24 22:36, Christoph Hellwig wrote:
> Please document this very clearly in the commit message, and maybe also
> in code comments.
Just send v3 patches fixed for the comment. Thank you.
> I don't really understand how this is related.
Actually not related this to the nvme-cli issue as a result.
(The issue was failed ns_attach on the test.
Then at first seemed caused by the ns_attach delay from the test log for me.
Also from the nvme driver implementation investigation looked the
scan_work is possible to be delayed.
But the issue caused was found as the failure caused by the test
environment configuration.
So the issue resolved for now but still the scan_work is possible to be
delay I think.)
prev parent reply other threads:[~2026-04-25 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 14:11 [PATCH v2 0/2] scan_work improvement Tokunori Ikegami
2026-04-22 14:11 ` [PATCH v2 1/2] nvme: delete unnecessary empty lines Tokunori Ikegami
2026-04-22 14:11 ` [PATCH v2 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC Tokunori Ikegami
2026-04-23 5:57 ` Christoph Hellwig
2026-04-23 17:51 ` Tokunori Ikegami
2026-04-24 13:36 ` Christoph Hellwig
2026-04-25 13:16 ` Tokunori Ikegami [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=9d96e920-e52c-4946-ba40-332bae38d7db@gmail.com \
--to=ikegami.t@gmail.com \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.org \
/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