From: Mohit Kapoor <mohit.kap@samsung.com>
To: kbusch@kernel.org, fam@euphon.net, its@irrelevant.dk,
kwolf@redhat.com, linux-nvme@lists.infradead.org,
mreitz@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
stefanha@redhat.com
Cc: arun.kka@samsung.com, d.palani@samsung.com,
p.kalghatgi@samsung.com, javier.gonz@samsung.com,
k.jensen@samsung.com, prakash.v@samsung.com,
u.kishore@samsung.com
Subject: Re: [RFC PATCH : v3 2/2] Implementation of nvme-mi plugin in nvme-cli
Date: Mon, 6 Sep 2021 19:48:54 +0530 [thread overview]
Message-ID: <20210906141854.GD22632@test.sa.corp.samsungelectronics.net> (raw)
In-Reply-To: <1627981486-3369-1-git-send-email-mohit.kap@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
On Tue, Aug 03, 2021 at 02:34:46PM +0530, Mohit Kapoor wrote:
>From: mohit kapoor <mohit.kap@samsung.com>
>
>Subject: [RFC PATCH : v3 2/2] Implementation of nvme-mi plugin in nvme-cli
Hello All,
Request to kindly provide your valuable feedback for the patches shared
for nvme-mi over QEMU and nvme-cli.
Looking forward for any suggestions and improvements.
Regards,
Mohit Kapoor
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-09-06 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210803080737epcas5p1c9bd6ecde8700d1194748533a3812db6@epcas5p1.samsung.com>
2021-08-03 7:24 ` [RFC PATCH: v3 1/2] add mi device in qemu Padmakar Kalghatgi
2021-08-03 9:04 ` [RFC PATCH : v3 2/2] Implementation of nvme-mi plugin in nvme-cli Mohit Kapoor
2021-09-06 14:18 ` Mohit Kapoor [this message]
2021-08-18 6:01 ` [RFC PATCH: v3 1/2] add mi device in qemu Klaus Jensen
2021-08-19 16:34 ` Padmakar Kalghatgi
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=20210906141854.GD22632@test.sa.corp.samsungelectronics.net \
--to=mohit.kap@samsung.com \
--cc=arun.kka@samsung.com \
--cc=d.palani@samsung.com \
--cc=fam@euphon.net \
--cc=its@irrelevant.dk \
--cc=javier.gonz@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mreitz@redhat.com \
--cc=p.kalghatgi@samsung.com \
--cc=prakash.v@samsung.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=u.kishore@samsung.com \
/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