From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
linux-scsi@vger.kernel.org, jejb@linux.ibm.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
beanhuo@micron.com, jiajie.hao@mediatek.com,
chun-hung.wu@mediatek.com, cc.chou@mediatek.com,
asutoshd@codeaurora.org, chaotian.jing@mediatek.com,
matthias.bgg@gmail.com, alice.chao@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andy.teng@mediatek.com,
bvanassche@acm.org, huadian.liu@mediatek.com,
kuohong.wang@mediatek.com, cang@codeaurora.org,
linux-mediatek@lists.infradead.org, peter.wang@mediatek.com
Subject: Re: [PATCH v5 0/4] scsi: ufs: Refine error history and introduce event_notify vop
Date: Wed, 9 Dec 2020 12:23:23 -0500 [thread overview]
Message-ID: <160753457754.14816.15980863701992917932.b4-ty@oracle.com> (raw)
In-Reply-To: <20201205115901.26815-1-stanley.chu@mediatek.com>
On Sat, 5 Dec 2020 19:58:57 +0800, Stanley Chu wrote:
> This series refines error history functions and introduces a new event_notify vop to allow vendor to get notification of important events.
>
> Changes since v4:
> - Seperate patch sets according to Avri's suggestion
>
> Changes since v3:
> - Fix build warning in patch [8/8]
>
> [...]
Applied to 5.11/scsi-queue, thanks!
[1/4] scsi: ufs: Add error history for abort event in UFS Device W-LUN
https://git.kernel.org/mkp/scsi/c/eb3d2611df2e
[2/4] scsi: ufs: Refine error history functions
https://git.kernel.org/mkp/scsi/c/e965e5e00b23
[3/4] scsi: ufs: Introduce event_notify variant function
https://git.kernel.org/mkp/scsi/c/172614a9d0e8
[4/4] scsi: ufs-mediatek: Introduce event_notify implementation
https://git.kernel.org/mkp/scsi/c/ca1bb061d644
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-12-09 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 11:58 [PATCH v5 0/4] scsi: ufs: Refine error history and introduce event_notify vop Stanley Chu
2020-12-05 11:58 ` [PATCH v5 1/4] scsi: ufs: Add error history for abort event in UFS Device W-LUN Stanley Chu
2020-12-05 11:58 ` [PATCH v5 2/4] scsi: ufs: Refine error history functions Stanley Chu
2020-12-05 11:59 ` [PATCH v5 3/4] scsi: ufs: Introduce event_notify variant function Stanley Chu
2020-12-05 11:59 ` [PATCH v5 4/4] scsi: ufs-mediatek: Introduce event_notify implementation Stanley Chu
2020-12-07 22:53 ` [PATCH v5 0/4] scsi: ufs: Refine error history and introduce event_notify vop Martin K. Petersen
2020-12-09 17:23 ` 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=160753457754.14816.15980863701992917932.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=huadian.liu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@mediatek.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).