From: Joel Granados <j.granados@samsung.com>
To: <hch@lst.de>, <kbusch@kernel.org>
Cc: <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/1] nvme: Remove unused enum constants in nvme.h
Date: Tue, 19 Jul 2022 23:17:31 +0200 [thread overview]
Message-ID: <20220719211731.zwdeglvake3egytl@localhost> (raw)
In-Reply-To: <20220622084859.1937878-1-j.granados@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Wed, Jun 22, 2022 at 10:48:58AM +0200, Joel Granados wrote:
> While working in include/linux/nvme.h, I noticed that there are enum
> constants that are not being used by the kernel. They are also not included
> in any UAPI directory. These variables were synced to keep up with nvme-cli
> in 48c9e85b2346 ("nvme: resync include/linux/nvme.h with nvmecli"). Since
> nvme-cli now uses libnvme which defines all the structures within itself,
> there is no need to synchronize any longer.
>
> There have been discussions to introduce functionality into the kernel that
> use some of these variables like in
> https://lore.kernel.org/all/1558278418-5702-1-git-send-email-akinobu.mita@gmail.com/
> but to my knowledge they have not made it upstream.
>
> This patch removes the enumerations that are not being used within the
> kernel.
>
> Please get back to me if I have missed something and these variables are
> indeed being used.
>
> Best
>
> Joel Granados (1):
> nvme: Remove unused enum constants
>
> include/linux/nvme.h | 32 --------------------------------
> 1 file changed, 32 deletions(-)
>
> --
> 2.30.2
>
>
Ping. Does this make sense? Or are we keeping these around for future
use?
Best
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-07-19 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220622085123eucas1p25f724850a5397fa90a0e26eb4d5af92f@eucas1p2.samsung.com>
2022-06-22 8:48 ` [PATCH 0/1] nvme: Remove unused enum constants in nvme.h Joel Granados
2022-06-22 8:48 ` [PATCH 1/1] nvme: Remove unused enum constants Joel Granados
2022-07-19 21:17 ` Joel Granados [this message]
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=20220719211731.zwdeglvake3egytl@localhost \
--to=j.granados@samsung.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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