From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: <linux-nvme@lists.infradead.org>, <sagi@grimberg.me>,
<kbusch@kernel.org>, <hch@lst.de>, <chaitanya.kulkarni@wdc.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [PATCH v2 0/2] Resync Linux and NVMe-cli nvme.h header
Date: Thu, 21 Jan 2021 09:09:45 +0000 [thread overview]
Message-ID: <20210121090948.8027-1-mgurtovoy@nvidia.com> (raw)
Hi Christoph/Sagi/Keith/Chaitanya,
This series introduce synchronization between the kernel
include/linux/nvme.h and nvme-cli linux/nvme.h to ease on maintainance
of both.
The changes for nvme-cli are in the structure of the linux/nvme.h header
file that will be divided to 2 parts: nvme-cli specific code and an
identical copy of the content of include/linux/nvme.h from Linux.
In this way, the resync process will be ease and whole the content of
include/linux/nvme.h will be pasted to that area. Individual commits to
this area will be forbidden and must go through kernel part first.
The additional to Linux include/linux/nvme.h is new enumerations from
NVMe 1.4 specification and the missing parts from nvme-cli that are
originated in common area of the code.
The structures and enumeration that were intruduced only to nvme-cli
were moved to part #1 in nvme-cli linux/nvme.h file and we can decide
whether we need them in the kernel as well. This can be done in future
step. Also new nvme-cli specifics that are not a must in the kernel and
are not in the common code structures/enums can go there.
To test this I run some basic commands as:
- nvme list
- nvme list -v
- nvme list-subsys
- nvme connect/disconnect
- nvme id-ctrl
- nvme id-ns
changes from V1:
- Added Reviewed-by signature for patch 1/2 (from Hannes)
- Added resync patch 2/2
- Added resync nvme-cli patch 1/1
Max Gurtovoy (2):
nvme: update enumerations for status codes
nvme: resync header file with common nvme-cli tool
include/linux/nvme.h | 90 +++++++++++++++++++++++++++++++++++---------
1 file changed, 72 insertions(+), 18 deletions(-)
--
2.25.4
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-21 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 9:09 Max Gurtovoy [this message]
2021-01-21 9:09 ` [PATCH nvme-cli 1/1] align Linux kernel nvme.h to nvme-cli Max Gurtovoy
2021-01-21 9:09 ` [PATCH 1/2] nvme: update enumerations for status codes Max Gurtovoy
2021-01-27 17:46 ` Christoph Hellwig
2021-01-21 9:09 ` [PATCH 2/2] nvme: resync header file with common nvme-cli tool Max Gurtovoy
2021-01-27 17:47 ` Christoph Hellwig
2021-02-09 15:07 ` Max Gurtovoy
2021-02-09 15:35 ` Christoph Hellwig
2021-02-11 13:01 ` Max Gurtovoy
2021-02-15 1:33 ` Chaitanya Kulkarni
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=20210121090948.8027-1-mgurtovoy@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).