From: Markus Elfring <Markus.Elfring@web.de>
To: Alexandr Sapozhnikov <alsp705@gmail.com>,
linux-nvme@lists.infradead.org, lvc-project@linuxtesting.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Chaitanya Kulkarni <kch@nvidia.com>,
Christoph Hellwig <hch@lst.de>, Daniel Wagner <wagi@kernel.org>,
James Smart <james.smart@broadcom.com>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] nvme: target: fix error checking in nvmet_fc_schedule_delete_assoc()
Date: Fri, 3 Oct 2025 15:25:23 +0200 [thread overview]
Message-ID: <d636ad52-2ec6-4b5c-9ded-a7dc1e1291be@web.de> (raw)
In-Reply-To: <20251002092202.11-1-alsp705@gmail.com>
> The nvmet_fc_tgtport_get() function may return an error.
Would a corresponding imperative wording become helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17#n94
Regards,
Markus
prev parent reply other threads:[~2025-10-03 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:22 Alexandr Sapozhnkiov
2025-10-03 10:13 ` Christoph Hellwig
2025-10-06 12:44 ` Daniel Wagner
2025-10-03 13:25 ` Markus Elfring [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=d636ad52-2ec6-4b5c-9ded-a7dc1e1291be@web.de \
--to=markus.elfring@web.de \
--cc=alsp705@gmail.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lvc-project@linuxtesting.org \
--cc=sagi@grimberg.me \
--cc=wagi@kernel.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
all inboxes | Powered by JetHome®