From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Po-Wen Kao <powen.kao@mediatek.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
<wsd_upstream@mediatek.com>, <peter.wang@mediatek.com>,
<stanley.chu@mediatek.com>, <alice.chao@mediatek.com>,
<naomi.chu@mediatek.com>, <chun-hung.wu@mediatek.com>,
<cc.chou@mediatek.com>, <eddie.huang@mediatek.com>
Subject: Re: [PATCH v1 0/4] ufs: Introduce MCQ Quirks for MediaTek host
Date: Wed, 14 Jun 2023 21:46:05 -0400 [thread overview]
Message-ID: <yq1fs6twl9m.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230612085817.12275-1-powen.kao@mediatek.com> (Po-Wen Kao's message of "Mon, 12 Jun 2023 16:58:08 +0800")
Po-Wen,
> Introduce quirks for non-standard part of UFSHCI and address Bart's comment
> from last patch
Applied to 6.5/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-06-15 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 8:58 Po-Wen Kao
2023-06-12 8:58 ` [PATCH v1 1/4] scsi: ufs: core: Add host quirk UFSHCD_QUIRK_MCQ_BROKEN_INTR Po-Wen Kao
2023-06-12 8:58 ` [PATCH v1 2/4] scsi: ufs: core: Add host quirk UFSHCD_QUIRK_MCQ_BROKEN_RTC Po-Wen Kao
2023-06-12 8:58 ` [PATCH v1 3/4] scsi: ufs: ufs-mediatek: Set UFSHCD_QUIRK_MCQ_BROKEN_INTR quirk Po-Wen Kao
2023-06-12 8:58 ` [PATCH v1 4/4] scsi: ufs: ufs-mediatek: Set UFSHCD_QUIRK_MCQ_BROKEN_RTC quirk Po-Wen Kao
2023-06-12 14:40 ` [PATCH v1 0/4] ufs: Introduce MCQ Quirks for MediaTek host Bart Van Assche
2023-06-12 15:27 ` Stanley Chu
2023-06-15 1:46 ` Martin K. Petersen [this message]
2023-06-22 1:26 ` 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=yq1fs6twl9m.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alice.chao@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=cc.chou@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=eddie.huang@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=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=stanley.chu@mediatek.com \
--cc=wsd_upstream@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
all inboxes | Powered by JetHome®