From: Christoph Hellwig <hch@lst.de>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: hare@suse.de, kbusch@kernel.org, hch@lst.de,
linux-nvme@lists.infradead.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] nvme-keyring: mark nvme_dhchap_psk_hash() as static inline
Date: Mon, 3 Nov 2025 12:46:43 +0100 [thread overview]
Message-ID: <20251103114643.GC15280@lst.de> (raw)
In-Reply-To: <20251102031701.69920-1-ckulkarnilinux@gmail.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-11-03 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 3:17 [PATCH] nvme-keyring: mark nvme_dhchap_psk_hash() as static inline Chaitanya Kulkarni
2025-11-03 11:46 ` Christoph Hellwig [this message]
2025-11-03 15:35 ` 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=20251103114643.GC15280@lst.de \
--to=hch@lst.de \
--cc=ckulkarnilinux@gmail.com \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox