From: Sagi Grimberg <sagi@grimberg.me>
To: Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>,
Keith Busch <kbusch@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvmet: add a missing endianess conversion in nvmet_execute_admin_connect
Date: Tue, 28 Jan 2025 10:03:03 +0200 [thread overview]
Message-ID: <bf553543-5bf5-4e97-8b17-7a96cd2c3c01@grimberg.me> (raw)
In-Reply-To: <20250128075539.693870-3-hch@lst.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2025-01-28 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:55 endian fixes for nvmet Christoph Hellwig
2025-01-28 7:55 ` [PATCH 1/2] nvmet: the result field in nvmet_alloc_ctrl_args is little endian Christoph Hellwig
2025-01-28 8:02 ` Sagi Grimberg
2025-01-28 7:55 ` [PATCH 2/2] nvmet: add a missing endianess conversion in nvmet_execute_admin_connect Christoph Hellwig
2025-01-28 8:03 ` Sagi Grimberg [this message]
2025-01-28 15:07 ` endian fixes for nvmet 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=bf553543-5bf5-4e97-8b17-7a96cd2c3c01@grimberg.me \
--to=sagi@grimberg.me \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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