From: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
To: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@suse.de>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>,
lkml <linux-kernel@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Subject: [PATCH 0/2 v2] scsi: ftrace based scsi tracing feature
Date: Mon, 01 Feb 2010 13:55:37 +0900 [thread overview]
Message-ID: <4B665EC9.6000608@jp.fujitsu.com> (raw)
Hi,
This is v2 patch series of SCSI trace.
Changelog from v1:
- fixed variable length command handling (DIF_TYPE2 case only)
- moved scsi trace functions from kernel/trace/scsitrace.c to
drivers/scsi/scsi_trace.c
Here are the links to the discussions on v1:
[PATCH 0/2] scsi: ftrace based scsi tracing feature
http://marc.info/?l=linux-scsi&m=126396981308416&w=2
[PATCH 1/2] scsi: add __print_hex() to ftrace
http://marc.info/?l=linux-scsi&m=126396984308451&w=2
[PATCH 2/2] scsi: add scsi trace core function and put trace points
http://marc.info/?l=linux-scsi&m=126396987608486&w=2
This patchset applies to 2.6.33-rc6.
Thanks,
Kei
WARNING: multiple messages have this Message-ID (diff)
From: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
To: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@suse.de>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Martin Peterson <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Joe Perches <joe@perches.com>
Cc: Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>,
lkml <linux-kernel@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Subject: [PATCH 0/2 v2] scsi: ftrace based scsi tracing feature
Date: Mon, 01 Feb 2010 13:55:37 +0900 [thread overview]
Message-ID: <4B665EC9.6000608@jp.fujitsu.com> (raw)
Hi,
This is v2 patch series of SCSI trace.
Changelog from v1:
- fixed variable length command handling (DIF_TYPE2 case only)
- moved scsi trace functions from kernel/trace/scsitrace.c to
drivers/scsi/scsi_trace.c
Here are the links to the discussions on v1:
[PATCH 0/2] scsi: ftrace based scsi tracing feature
http://marc.info/?l=linux-scsi&m=126396981308416&w=2
[PATCH 1/2] scsi: add __print_hex() to ftrace
http://marc.info/?l=linux-scsi&m=126396984308451&w=2
[PATCH 2/2] scsi: add scsi trace core function and put trace points
http://marc.info/?l=linux-scsi&m=126396987608486&w=2
This patchset applies to 2.6.33-rc6.
Thanks,
Kei
next reply other threads:[~2010-02-01 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 4:55 Kei Tokunaga [this message]
2010-02-01 4:55 ` [PATCH 0/2 v2] scsi: ftrace based scsi tracing feature Kei Tokunaga
2010-02-01 5:05 ` [PATCH 1/2 v2] scsi: add __print_hex() to ftrace Kei Tokunaga
2010-02-01 5:05 ` Kei Tokunaga
2010-02-01 5:07 ` [PATCH 2/2 v2] scsi: add scsi trace core function and put trace points Kei Tokunaga
2010-02-01 5:07 ` Kei Tokunaga
2010-02-02 23:12 ` Martin K. Petersen
2010-02-03 5:55 ` Kei Tokunaga
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=4B665EC9.6000608@jp.fujitsu.com \
--to=tokunaga.keiich@jp.fujitsu.com \
--cc=James.Bottomley@suse.de \
--cc=fweisbec@gmail.com \
--cc=kusumi.tomohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=xiaoguangrong@cn.fujitsu.com \
/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.