From: Keith Busch <kbusch@kernel.org>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: hare@suse.de, 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 08:35:09 -0700 [thread overview]
Message-ID: <aQjLrZ5zXWrUtMGI@kbusch-mbp> (raw)
In-Reply-To: <20251102031701.69920-1-ckulkarnilinux@gmail.com>
On Sat, Nov 01, 2025 at 08:17:01PM -0700, Chaitanya Kulkarni wrote:
> Fix build warning when CONFIG_NVME_KEYRING is not enabled:
>
> include/linux/nvme-keyring.h:57:4: warning: no previous prototype for
> function 'nvme_dhchap_psk_hash' [-Wmissing-prototypes]
>
> The nvme_dhchap_psk_hash() stub function in the #else block is missing
> the 'static inline' qualifiers that all other stub functions in the same
> block have. Add them to fix the warning.
Thanks, applied to nvme-6.19.
prev parent reply other threads:[~2025-11-03 15:35 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
2025-11-03 15:35 ` Keith Busch [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=aQjLrZ5zXWrUtMGI@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=ckulkarnilinux@gmail.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--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