From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhad.com" <mingo@redhad.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"rajatja@google.com" <rajatja@google.com>
Subject: Re: [RESEND PATCH v1 2/2] trace: events: block: Add tag in block trace events
Date: Mon, 16 Apr 2018 20:49:52 +0000 [thread overview]
Message-ID: <51266d3243acdf73e800a0d283473cc85a52a388.camel@wdc.com> (raw)
In-Reply-To: <64d6073b28b140cda3e5870a54e0a7bc@SIWEX5A.sing.micron.com>
T24gTW9uLCAyMDE4LTA0LTE2IGF0IDE0OjMzICswMDAwLCBCZWFuIEh1byAoYmVhbmh1bykgd3Jv
dGU6DQo+IFsgLi4uIF0NCj4gLQlUUF9wcmludGsoIiVkLCVkICVzICglcykgJWxsdSArICV1IFsl
ZF0iLA0KPiArCVRQX3ByaW50aygiJWQsJWQgJXMgKCVzKSAlbGx1ICsgJXUgdGFnPSVkIFslZF0i
LA0KPiBbIC4uLiBdDQo+IC0JVFBfcHJpbnRrKCIlZCwlZCAlcyAoJXMpICVsbHUgKyAldSBbJWRd
IiwNCj4gKwlUUF9wcmludGsoIiVkLCVkICVzICglcykgJWxsdSArICV1IHRhZz0lZCBbJWRdIiwN
Cj4gWyAuLi4gXQ0KDQpXaGljaCB0b29scyBwcm9jZXNzIHRoZXNlIHN0cmluZ3M/IEhhcyBpdCBi
ZWVuIHZlcmlmaWVkIHdoZXRoZXIgb3Igbm90DQp0aGUgdG9vbHMgdGhhdCBwcm9jZXNzIHRoZXNl
IHN0cmluZ3Mgc3RpbGwgd29yayBmaW5lIHdpdGggdGhpcyBwYXRjaA0KYXBwbGllZD8NCg0KVGhh
bmtzLA0KDQpCYXJ0Lg0KDQoNCg0K
next prev parent reply other threads:[~2018-04-16 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 14:33 [RESEND PATCH v1 2/2] trace: events: block: Add tag in block trace events Bean Huo (beanhuo)
2018-04-16 15:29 ` Steven Rostedt
2018-04-16 20:49 ` Bart Van Assche [this message]
2018-04-23 12:43 ` Steffen Maier
2018-04-23 13:34 ` Steven Rostedt
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=51266d3243acdf73e800a0d283473cc85a52a388.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhad.com \
--cc=rajatja@google.com \
--cc=rostedt@goodmis.org \
/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