From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: Ohad Sharabi <Ohad.Sharabi@wdc.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Stanislav Nijnikov <Stanislav.Nijnikov@wdc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Lemberg <Alex.Lemberg@wdc.com>
Subject: Re: [PATCH v3] scsi: ufs: add trace event for ufs upiu
Date: Mon, 26 Mar 2018 22:48:53 +0000 [thread overview]
Message-ID: <1522104532.3102.24.camel@wdc.com> (raw)
In-Reply-To: <1521961684-13588-1-git-send-email-ohad.sharabi@sandisk.com>
On Sun, 2018-03-25 at 10:08 +0300, Ohad Sharabi wrote:
> Add UFS Protocol Information Units(upiu) trace events for ufs driver,
> used to trace various ufs transaction types- command, task-management
> and device management.
> The trace-point format is generic and can be easily adapted to trace
> other upius if needed.
> Currently tracing ufs transaction of type 'device management', which
> this patch introduce, cannot be obtained from any other trace.
> Device management transactions are used for communication with the
> device such as reading and writing descriptor or attributes etc.
>
> v2->v3:
> - modify args 3,4 of trace_ufshcd_upiu to be void *
>
> v1->v2:
> - split to transaction specific functions (fix warnings and simplifies
> code)
> - adding traces when sending query command
The changelog for a patch should appear under the three hyphens such that it
gets discarded automatically by tools like "git am". Martin will have to
remove the above changelog manually. Anyway:
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2018-03-26 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 7:08 Ohad Sharabi
2018-03-25 13:44 ` Stanislav Nijnikov
2018-03-26 22:48 ` Bart Van Assche [this message]
2018-03-28 9:42 Ohad Sharabi
2018-03-28 22:03 ` Martin K. Petersen
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=1522104532.3102.24.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=Alex.Lemberg@wdc.com \
--cc=Ohad.Sharabi@wdc.com \
--cc=Stanislav.Nijnikov@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
Powered by JetHome