From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: trace: add disk name to tracepoints
Date: Thu, 31 May 2018 18:47:59 +0200 [thread overview]
Message-ID: <20180531164759.GA31353@lst.de> (raw)
In-Reply-To: <20180530132049.5890-1-jthumshirn@suse.de>
On Wed, May 30, 2018@03:20:49PM +0200, Johannes Thumshirn wrote:
> Add disk name to tracepoints so we can better destinguish between
> individual disks in the trace output.
Doesn't apply to the nvme-4.18 branch, please resend.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>,
Sagi Grimberg <sagi@grimberg.me>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] nvme: trace: add disk name to tracepoints
Date: Thu, 31 May 2018 18:47:59 +0200 [thread overview]
Message-ID: <20180531164759.GA31353@lst.de> (raw)
In-Reply-To: <20180530132049.5890-1-jthumshirn@suse.de>
On Wed, May 30, 2018 at 03:20:49PM +0200, Johannes Thumshirn wrote:
> Add disk name to tracepoints so we can better destinguish between
> individual disks in the trace output.
Doesn't apply to the nvme-4.18 branch, please resend.
next prev parent reply other threads:[~2018-05-31 16:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 13:20 [PATCH] nvme: trace: add disk name to tracepoints Johannes Thumshirn
2018-05-30 13:20 ` Johannes Thumshirn
2018-05-30 23:06 ` Sagi Grimberg
2018-05-30 23:06 ` Sagi Grimberg
2018-05-31 16:47 ` Christoph Hellwig [this message]
2018-05-31 16:47 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 13:51 [PATCH v4 0/2] nvme: add controller id and " Johannes Thumshirn
2018-06-26 13:51 ` [PATCH] nvme: trace: add " Johannes Thumshirn
2018-06-26 13:51 ` Johannes Thumshirn
2018-06-26 15:01 ` Keith Busch
2018-06-26 15:01 ` Keith Busch
2018-06-27 7:33 ` Johannes Thumshirn
2018-06-27 7:33 ` Johannes Thumshirn
2018-06-27 8:06 ` Sagi Grimberg
2018-06-27 8:06 ` Sagi Grimberg
2018-06-27 10:00 ` Johannes Thumshirn
2018-06-27 10:00 ` Johannes Thumshirn
2018-06-27 23:43 ` Keith Busch
2018-06-27 23:43 ` Keith Busch
2018-06-28 0:59 ` Keith Busch
2018-06-28 0:59 ` Keith Busch
2018-06-28 7:44 ` Johannes Thumshirn
2018-06-28 7:44 ` Johannes Thumshirn
2018-06-28 14:34 ` Sagi Grimberg
2018-06-28 14:34 ` Sagi Grimberg
2018-06-28 15:02 ` Keith Busch
2018-06-28 15:02 ` Keith Busch
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=20180531164759.GA31353@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.