LKML Archive on
help / color / mirror / Atom feed
From: "Gilad Broner" <>
To: "Steven Rostedt" <>
Cc: "Gilad Broner" <>,,,,,,,,,,
	"Lee Susman" <>,
	"Sujit Reddy Thumma" <>,
	"Vinayak Holikatti" <>,
	"James E.J. Bottomley" <>,
	"Ingo Molnar" <>
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: <> (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

      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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v5 3/3] scsi: ufs: add trace events and dump prints for debug' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).