From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: stanley.chu@mediatek.com, beanhuo@micron.com, jejb@linux.ibm.com,
Bean Huo <huobean@gmail.com>,
alim.akhtar@samsung.com, rostedt@goodmis.org, bvanassche@acm.org,
tomas.winkler@intel.com, asutoshd@codeaurora.org,
avri.altman@wdc.com, cang@codeaurora.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Several changes for the UPIU trace
Date: Wed, 13 Jan 2021 00:48:22 -0500 [thread overview]
Message-ID: <161050726819.14224.15923940659426155067.b4-ty@oracle.com> (raw)
In-Reply-To: <20210105113446.16027-1-huobean@gmail.com>
On Tue, 5 Jan 2021 12:34:40 +0100, Bean Huo wrote:
> Changelog:
>
> V3--v4:
> 1. Rebase patch onto 5.12/scsi-queue
> 2. Incorporate Avri's suggestion in patch 2/6
>
> V2--V3:
> 1. Fix a typo in patch 1/6 (Reported-by: Joe Perches <joe@perches.com>)
>
> [...]
Applied to 5.12/scsi-queue, thanks!
[1/6] scsi: ufs: Remove stringize operator '#' restriction
https://git.kernel.org/mkp/scsi/c/c7c730ac6a88
[2/6] scsi: ufs: Use __print_symbolic() for UFS trace string print
https://git.kernel.org/mkp/scsi/c/28fa68fc557a
[3/6] scsi: ufs: Don't call trace_ufshcd_upiu() in case trace poit is disabled
https://git.kernel.org/mkp/scsi/c/9d5095e74c83
[4/6] scsi: ufs: Distinguish between query REQ and query RSP in query trace
https://git.kernel.org/mkp/scsi/c/be20b51cfd85
[5/6] scsi: ufs: Distinguish between TM request UPIU and response UPIU in TM UPIU trace
https://git.kernel.org/mkp/scsi/c/0ed083e91662
[6/6] scsi: ufs: Make UPIU trace easier differentiate among CDB, OSF, and TM
https://git.kernel.org/mkp/scsi/c/867fdc2d6e34
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-01-13 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 11:34 [PATCH v4 0/6] Several changes for the UPIU trace Bean Huo
2021-01-05 11:34 ` [PATCH v4 1/6] scsi: ufs: Remove stringize operator '#' restriction Bean Huo
2021-01-05 11:34 ` [PATCH v4 2/6] scsi: ufs: Use __print_symbolic() for UFS trace string print Bean Huo
2021-01-05 11:34 ` [PATCH v4 3/6] scsi: ufs: Don't call trace_ufshcd_upiu() in case trace poit is disabled Bean Huo
2021-01-05 11:34 ` [PATCH v4 4/6] scsi: ufs: Distinguish between query REQ and query RSP in query trace Bean Huo
2021-01-05 11:34 ` [PATCH v4 5/6] scsi: ufs: Distinguish between TM request UPIU and response UPIU in TM UPIU trace Bean Huo
2021-01-05 11:34 ` [PATCH v4 6/6] scsi: ufs: Make UPIU trace easier differentiate among CDB, OSF, and TM Bean Huo
2021-01-08 3:29 ` [PATCH v4 0/6] Several changes for the UPIU trace Martin K. Petersen
2021-01-13 5:48 ` Martin K. Petersen [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=161050726819.14224.15923940659426155067.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).