From: Michal Krakowiak <michal.krakowiak@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Michal Krakowiak <michal.krakowiak@intel.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>,
Keith Busch <kbusch@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] nvme: trace: parse format nvm command in detail
Date: Thu, 28 Jan 2021 13:25:01 +0100 [thread overview]
Message-ID: <20210128122501.GA2579222@michal-desk> (raw)
In-Reply-To: <20210127174606.GA28180@lst.de>
Thanks,
I'd like to ask about future nvme tracing development: Will preparing
similar patches (for more commands) be welcome? I'd like to do it, but I
got some concerns after the discussion raised due to this patch.
On Wed, Jan 27, 2021 at 06:46:06PM +0100, Christoph Hellwig wrote:
>Thanks,
>
>applied to nvme-5.12.
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-28 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 15:53 [PATCH] nvme: trace: parse format nvm command in detail Michal Krakowiak
2021-01-04 16:02 ` Keith Busch
2021-01-06 9:00 ` Christoph Hellwig
2021-01-08 22:34 ` Keith Busch
2021-01-09 0:12 ` Dan Williams
2021-01-11 17:01 ` Keith Busch
2021-01-11 17:10 ` Dan Williams
2021-01-11 17:50 ` Keith Busch
2021-01-11 20:15 ` Michal Krakowiak
2021-01-12 8:33 ` Christoph Hellwig
2021-01-05 19:31 ` Minwoo Im
2021-01-27 17:46 ` Christoph Hellwig
2021-01-28 12:25 ` Michal Krakowiak [this message]
2021-01-28 12:39 ` Christoph Hellwig
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=20210128122501.GA2579222@michal-desk \
--to=michal.krakowiak@linux.intel.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michal.krakowiak@intel.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