From: Keith Busch <kbusch@kernel.org>
To: hare@kernel.org
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 1/3] nvme-auth: open-code single-use macros
Date: Mon, 29 Jan 2024 08:13:42 -0700 [thread overview]
Message-ID: <ZbfApnvCAQVw_vMD@kbusch-mbp> (raw)
In-Reply-To: <20240127093746.40246-2-hare@kernel.org>
On Sat, Jan 27, 2024 at 10:37:44AM +0100, hare@kernel.org wrote:
> From: Hannes Reinecke <hare@suse.de>
>
> No point in having macros just for a single function nvme_auth_submit().
> Open-code them into the caller.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
Thanks, applied for nvme-6.8.
next prev parent reply other threads:[~2024-01-29 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 9:37 [PATCHv3 0/3] nvme: enable retries for authentication commands hare
2024-01-27 9:37 ` [PATCH 1/3] nvme-auth: open-code single-use macros hare
2024-01-29 5:58 ` Christoph Hellwig
2024-01-29 14:19 ` Sagi Grimberg
2024-01-29 15:13 ` Keith Busch [this message]
2024-01-27 9:37 ` [PATCH 2/3] nvme: simplify __nvme_submit_sync_cmd() calling conventions hare
2024-01-27 18:00 ` Nicky Chorley
2024-01-29 5:59 ` Christoph Hellwig
2024-01-27 9:37 ` [PATCH 3/3] nvme: enable retries for authentication commands hare
2024-01-29 6:00 ` Christoph Hellwig
2024-01-29 6:24 ` Hannes Reinecke
2024-01-29 11:12 ` [PATCHv3 0/3] " Chaitanya Kulkarni
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 6:39 [PATCHv4 " hare
2024-01-29 6:39 ` [PATCH 1/3] nvme-auth: open-code single-use macros hare
2024-01-29 20:00 ` Sagi Grimberg
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=ZbfApnvCAQVw_vMD@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox