public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
To: "linux-scsi@vger.kernel.org" <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 K. Petersen" <martin.petersen@oracle.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 v3] scsi: ftrace based scsi tracing feature
Date: Mon, 15 Feb 2010 18:33:01 +0900	[thread overview]
Message-ID: <4B7914CD.8020508@jp.fujitsu.com> (raw)

Hi,

This is v3 patch series of SCSI trace.  Since there has been no
more new feedback on v2 for about a week, I've decided to post
this.

Changelog from v2:

  - fixed variable length command handling (removed the
    assumption that READ/WRITE(32) is only called if protection
    is enabled.)

Here are the links to the discussions on v2:

  [PATCH 0/2 v2] scsi: ftrace based scsi tracing feature
    http://marc.info/?l=linux-scsi&m=126500018231317&w=2
  [PATCH 1/2 v2] scsi: add __print_hex() to ftrace
    http://marc.info/?l=linux-scsi&m=126500074718183&w=2
  [PATCH 2/2 v2] scsi: add scsi trace core function and put trace
points
    http://marc.info/?l=linux-scsi&m=126500087718320&w=2

This patchset applies to 2.6.33-rc8.

Thanks,
Kei


             reply	other threads:[~2010-02-15  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15  9:33 Kei Tokunaga [this message]
2010-02-15  9:46 ` [PATCH 1/2 v3] scsi: add __print_hex() to ftrace Kei Tokunaga
2010-02-15  9:46 ` [PATCH 2/2 v3] scsi: add scsi trace core functions and put trace points 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=4B7914CD.8020508@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=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox