From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: sthumma@codeaurora.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, marc.w.gonzalez@free.fr,
subhashj@codeaurora.org, chun-hung.wu@mediatek.com,
kuohong.wang@mediatek.com, peter.wang@mediatek.com,
evgreen@chromium.org, avri.altman@wdc.com,
linux-mediatek@lists.infradead.org, ygardi@codeaurora.org,
alim.akhtar@samsung.com, andy.teng@mediatek.com,
matthias.bgg@gmail.com, pedrom.sousa@synopsys.com,
linux-arm-kernel@lists.infradead.org, beanhuo@micron.com
Subject: Re: [PATCH v3 0/4] scsi: ufs: Provide fatal and auto-hibern8 error history
Date: Thu, 11 Jul 2019 21:20:18 -0400 [thread overview]
Message-ID: <yq1h87s6obx.fsf@oracle.com> (raw)
In-Reply-To: <1562765901-18328-1-git-send-email-stanley.chu@mediatek.com> (Stanley Chu's message of "Wed, 10 Jul 2019 21:38:17 +0800")
Stanley,
> This patchset provides more information of fatal errros and
> auto-hibern8 errors to improve debugging by keeping their error
> history as completed as possible.
Applied to 5.4/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-12 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 13:38 [PATCH v3 0/4] scsi: ufs: Provide fatal and auto-hibern8 error history Stanley Chu
2019-07-10 13:38 ` [PATCH v3 1/4] scsi: ufs: Change names related to " Stanley Chu
2019-07-10 13:38 ` [PATCH v3 2/4] scsi: ufs: Add fatal and auto-hibern8 " Stanley Chu
2019-07-10 13:38 ` [PATCH v3 3/4] scsi: ufs: Do not reset error history during host reset Stanley Chu
2019-07-10 13:38 ` [PATCH v3 4/4] scsi: ufs: Add history of fatal events Stanley Chu
2019-07-11 6:15 ` Avri Altman
2019-07-12 1:20 ` 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=yq1h87s6obx.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=chun-hung.wu@mediatek.com \
--cc=evgreen@chromium.org \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=matthias.bgg@gmail.com \
--cc=pedrom.sousa@synopsys.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@mediatek.com \
--cc=sthumma@codeaurora.org \
--cc=subhashj@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).