From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2] nvme: trace: add disk name to tracepoints
Date: Mon, 4 Jun 2018 14:08:50 +0200 [thread overview]
Message-ID: <20180604120850.GA29495@lst.de> (raw)
In-Reply-To: <5af6f3ad-0932-ae45-a6f2-90e8e45726c5@grimberg.me>
On Mon, Jun 04, 2018@02:48:57PM +0300, Sagi Grimberg wrote:
>
>> Add disk name to tracepoints so we can better destinguish between
>> individual disks in the trace output.
>>
>> Signed-off-by: Johannes Thumshirn <jthumshirn at suse.de>
>> Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
>
> Nit: s/destinguish/distinguish/g
>
> Christoph, can you fix it up when applying or you want me
> to do it?
I can fix it up.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Johannes Thumshirn <jthumshirn@suse.de>,
Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2] nvme: trace: add disk name to tracepoints
Date: Mon, 4 Jun 2018 14:08:50 +0200 [thread overview]
Message-ID: <20180604120850.GA29495@lst.de> (raw)
In-Reply-To: <5af6f3ad-0932-ae45-a6f2-90e8e45726c5@grimberg.me>
On Mon, Jun 04, 2018 at 02:48:57PM +0300, Sagi Grimberg wrote:
>
>> Add disk name to tracepoints so we can better destinguish between
>> individual disks in the trace output.
>>
>> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
>> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
>
> Nit: s/destinguish/distinguish/g
>
> Christoph, can you fix it up when applying or you want me
> to do it?
I can fix it up.
next prev parent reply other threads:[~2018-06-04 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 7:56 [PATCH v2] nvme: trace: add disk name to tracepoints Johannes Thumshirn
2018-06-04 7:56 ` Johannes Thumshirn
2018-06-04 11:48 ` Sagi Grimberg
2018-06-04 11:48 ` Sagi Grimberg
2018-06-04 12:08 ` Christoph Hellwig [this message]
2018-06-04 12:08 ` 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=20180604120850.GA29495@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.