From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvme: reduce a repeated ZNS check
Date: Thu, 2 May 2024 09:13:38 +0200 [thread overview]
Message-ID: <20240502071338.GC31379@lst.de> (raw)
In-Reply-To: <20240502063438.422046-3-joshi.k@samsung.com>
On Thu, May 02, 2024 at 12:04:38PM +0530, Kanchan Joshi wrote:
> Modify nvme_update_ns_info_block() to eliminate the repeated check for
> ZNS.
Not sure there is much of a point do de-duplicate two instances of
compile time condition + trivial const comparison?
next prev parent reply other threads:[~2024-05-02 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240502064149epcas5p4be127b8e22874b76bb41ce25c29263f9@epcas5p4.samsung.com>
2024-05-02 6:34 ` [PATCH 0/2] cleanup Kanchan Joshi
2024-05-02 6:34 ` [PATCH 1/2] nvme: remove sgs and sws Kanchan Joshi
2024-05-02 7:12 ` Christoph Hellwig
2024-05-03 7:36 ` Sagi Grimberg
2024-05-02 6:34 ` [PATCH 2/2] nvme: reduce a repeated ZNS check Kanchan Joshi
2024-05-02 7:13 ` Christoph Hellwig [this message]
2024-05-02 8:44 ` Kanchan Joshi
2024-05-03 7:38 ` 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=20240502071338.GC31379@lst.de \
--to=hch@lst.de \
--cc=joshi.k@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox