From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: move nvme_dsm_range size check to _nvme_check_size()
Date: Tue, 27 Feb 2024 16:21:43 +0100 [thread overview]
Message-ID: <20240227152143.GA14722@lst.de> (raw)
In-Reply-To: <c8f19c2c-82fe-4cc3-b408-bf8040222fba@linux.alibaba.com>
This is not a check for a spec provided struct size, so it should
not be grouped with them.
next prev parent reply other threads:[~2024-02-27 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 3:29 [PATCH] nvme: move nvme_dsm_range size check to _nvme_check_size() Guixin Liu
2024-02-27 6:05 ` Guixin Liu
2024-02-27 15:21 ` Christoph Hellwig [this message]
2024-03-07 9:39 ` 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=20240227152143.GA14722@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kanie@linux.alibaba.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.