From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH v2 1/2] nvme: Cleanup the definition of the controller config register fields
Date: Thu, 13 Feb 2025 08:05:14 +0100 [thread overview]
Message-ID: <20250213070514.GA21130@lst.de> (raw)
In-Reply-To: <20250213065000.598443-2-dlemoal@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-02-13 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 6:49 [PATCH v2 0/2] Cleanup controller configuration register handling Damien Le Moal
2025-02-13 6:49 ` [PATCH v2 1/2] nvme: Cleanup the definition of the controller config register fields Damien Le Moal
2025-02-13 7:05 ` Christoph Hellwig [this message]
2025-02-13 17:44 ` Chaitanya Kulkarni
2025-02-13 6:50 ` [PATCH v2 2/2] nvmet: Use enum definitions instead of hardcoded values Damien Le Moal
2025-02-18 15:46 ` [PATCH v2 0/2] Cleanup controller configuration register handling 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=20250213070514.GA21130@lst.de \
--to=hch@lst.de \
--cc=dlemoal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox