From: Martin Wilck <martin.wilck@suse.com>
To: "kbusch@kernel.org" <kbusch@kernel.org>,
"Chaitanya.Kulkarni@wdc.com" <Chaitanya.Kulkarni@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Hannes Reinecke <hare@suse.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"james.smart@broadcom.com" <james.smart@broadcom.com>,
"Steve.Schremmer@netapp.com" <Steve.Schremmer@netapp.com>,
"marting@netapp.com" <marting@netapp.com>,
"hch@lst.de" <hch@lst.de>,
"Matias.Bjorling@wdc.com" <Matias.Bjorling@wdc.com>,
"johnm@netapp.com" <johnm@netapp.com>
Subject: Re: RFC: nvme-cli: add "nvme monitor" subcommand
Date: Tue, 26 Jan 2021 20:24:03 +0000 [thread overview]
Message-ID: <efda478fa8c3eb79a3916a395c62be9671b6ff5d.camel@suse.com> (raw)
In-Reply-To: <BYAPR04MB4965D8F1CCBC27D60B242B7486BC9@BYAPR04MB4965.namprd04.prod.outlook.com>
On Tue, 2021-01-26 at 19:23 +0000, Chaitanya Kulkarni wrote:
> On 1/26/21 3:48 AM, Martin Wilck wrote:
> > Currently it handles only AENs and NVME-FC uevents, but it can be
> > extended to other protocols in the future.
> >
> > Following the "publish early" principle, I'm posting this here now.
> > My test results were positive so far.
> >
> > I've created a github PR with all the details here, please have a
> > look:
> >
> > https://github.com/linux-nvme/nvme-cli/pull/877
> >
> > Issues with the CI came up after I submitted this, I'm working on
> > that.
>
> I had this in mind for a while especially with AENs for ZNS and other
> device features.
>
> Can you please create a patchset and post it on the mailing list ?
> also
> please CC me.
Will do. I won't CC everyone on from the cc list of this post though,
I don't want to spam people too much.
Thanks
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Software Solutions Germany GmbH
HRB 36809, AG Nürnberg GF: Felix Imendörffer
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-01-26 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:41 RFC: nvme-cli: add "nvme monitor" subcommand Martin Wilck
2021-01-26 19:23 ` Chaitanya Kulkarni
2021-01-26 20:24 ` Martin Wilck [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=efda478fa8c3eb79a3916a395c62be9671b6ff5d.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Steve.Schremmer@netapp.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=johnm@netapp.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=marting@netapp.com \
--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