From: "Gilad Broner" <gbroner@codeaurora.org>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Gilad Broner" <gbroner@codeaurora.org>,
james.bottomley@hansenpartnership.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
linux-scsi-owner@vger.kernel.org, subhashj@codeaurora.org,
ygardi@codeaurora.org, draviv@codeaurora.org,
"Lee Susman" <lsusman@codeaurora.org>,
"Sujit Reddy Thumma" <sthumma@codeaurora.org>,
"Vinayak Holikatti" <vinholikatti@gmail.com>,
"James E.J. Bottomley" <jbottomley@parallels.com>,
"Ingo Molnar" <mingo@redhat.com>
Subject: Re: [PATCH v5 3/3] scsi: ufs: add trace events and dump prints for debug
Date: Thu, 12 Mar 2015 12:28:58 -0000 [thread overview]
Message-ID: <e5512089069a6b6f41288806512badb2.squirrel@codeaurora.org> (raw)
In-Reply-To: <20150310104357.0165cab6@gandalf.local.home>
> This and the auto_bkops_state is pretty much the same. Can't you use
> the same TP_printk() and just have a DECLARE_EVENT_CLASS? The trace
> point name is printed with the event to see different events.
I agree. will upload the fix in next patchset.
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-03-12 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:47 [PATCH v5 0/3] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-03-10 11:47 ` [PATCH v5 1/3] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-03-10 11:47 ` [PATCH v5 2/3] scsi: ufs: add debugfs for ufs Gilad Broner
2015-03-10 11:47 ` [PATCH v5 3/3] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-03-10 14:43 ` Steven Rostedt
2015-03-12 12:28 ` Gilad Broner [this message]
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=e5512089069a6b6f41288806512badb2.squirrel@codeaurora.org \
--to=gbroner@codeaurora.org \
--cc=draviv@codeaurora.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jbottomley@parallels.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsusman@codeaurora.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=santoshsy@gmail.com \
--cc=sthumma@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@codeaurora.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