From: Christoph Hellwig <hch@lst.de>
To: Caleb Sander <csander@purestorage.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/5] nvme: remove redundant status mask
Date: Wed, 31 Jan 2024 18:33:16 +0100 [thread overview]
Message-ID: <20240131173316.GF31567@lst.de> (raw)
In-Reply-To: <20240131164315.160042-2-csander@purestorage.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-01-31 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 16:43 [PATCH 1/5] nvme: return string as char *, not unsigned char * Caleb Sander
2024-01-31 16:43 ` [PATCH 2/5] nvme: remove redundant status mask Caleb Sander
2024-01-31 17:33 ` Christoph Hellwig [this message]
2024-01-31 20:54 ` Sagi Grimberg
2024-01-31 16:43 ` [PATCH 3/5] nvme: take const cmd pointer in read-only helpers Caleb Sander
2024-01-31 17:33 ` Christoph Hellwig
2024-01-31 20:55 ` Sagi Grimberg
2024-01-31 16:43 ` [PATCH 4/5] nvme: split out fabrics version of nvme_opcode_str() Caleb Sander
2024-01-31 17:34 ` Christoph Hellwig
2024-01-31 20:56 ` Sagi Grimberg
2024-01-31 16:43 ` [PATCH 5/5] nvme-fc: log human-readable opcode on timeout Caleb Sander
2024-01-31 17:34 ` Christoph Hellwig
2024-01-31 20:57 ` Sagi Grimberg
2024-01-31 17:33 ` [PATCH 1/5] nvme: return string as char *, not unsigned char * Christoph Hellwig
2024-01-31 20:54 ` Sagi Grimberg
2024-01-31 23:05 ` Chaitanya Kulkarni
2024-02-01 0:29 ` 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=20240131173316.GF31567@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=james.smart@broadcom.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.