From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.g.garry@oracle.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, alan.adamson@oracle.com
Subject: Re: [PATCH] nvme: fix endianness of command word prints in nvme_log_err_passthru()
Date: Thu, 3 Jul 2025 13:45:02 +0200 [thread overview]
Message-ID: <20250703114502.GC17686@lst.de> (raw)
In-Reply-To: <20250630162153.4040149-1-john.g.garry@oracle.com>
I tried to apply this to nvme-6.17, but it depend on the previous
cdw numbering fix in 6.16. I guess we'll want to pick this up after
6.17-rc1 unless there's a need to rush it into 6.16.
next prev parent reply other threads:[~2025-07-03 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 16:21 [PATCH] nvme: fix endianness of command word prints in nvme_log_err_passthru() John Garry
2025-06-30 16:44 ` Keith Busch
2025-07-01 15:51 ` alan.adamson
2025-07-03 11:45 ` Christoph Hellwig [this message]
2025-07-03 11:48 ` John Garry
2025-07-14 13:52 ` Christoph Hellwig
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=20250703114502.GC17686@lst.de \
--to=hch@lst.de \
--cc=alan.adamson@oracle.com \
--cc=axboe@kernel.dk \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.