From: Po-Wen Kao <powen.kao@mediatek.com>
To: <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>
Cc: <wsd_upstream@mediatek.com>, <peter.wang@mediatek.com>,
<stanley.chu@mediatek.com>, <powen.kao@mediatek.com>,
<alice.chao@mediatek.com>, <naomi.chu@mediatek.com>,
<chun-hung.wu@mediatek.com>, <cc.chou@mediatek.com>,
<eddie.huang@mediatek.com>
Subject: [PATCH v2 0/2] ufs: mcq: Share first hwq for dev comamnd and IO request
Date: Sat, 10 Jun 2023 10:15:50 +0800 [thread overview]
Message-ID: <20230610021553.1213-1-powen.kao@mediatek.com> (raw)
v1 -> v2:
- Remove accidentally added ufshcd_add_command_trace() call in
[PATCH v1 1/2]
- Add Test-by tag for both patch and refactor commit message
Po-Wen Kao (1):
scsi: ufs: core: Remove dedicated hwq for dev command
Stanley Chu (1):
scsi: ufs: mcq: Fix the incorrect OCS value for the device command
drivers/ufs/core/ufs-mcq.c | 14 ++++----------
drivers/ufs/core/ufshcd-priv.h | 1 -
drivers/ufs/core/ufshcd.c | 14 +++++++++-----
include/ufs/ufshcd.h | 1 -
4 files changed, 13 insertions(+), 17 deletions(-)
--
2.18.0
next reply other threads:[~2023-06-10 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 2:15 Po-Wen Kao [this message]
2023-06-10 2:15 ` [PATCH v2 1/2] scsi: ufs: mcq: Fix the incorrect OCS value for the device command Po-Wen Kao
2023-06-11 13:59 ` Bart Van Assche
2023-06-11 14:49 ` Stanley Chu
2023-06-11 15:19 ` Bart Van Assche
2023-06-10 2:15 ` [PATCH v2 2/2] scsi: ufs: core: Remove dedicated hwq for dev command Po-Wen Kao
2023-06-10 3:00 ` Stanley Chu
2023-06-11 14:04 ` Bart Van Assche
2023-06-15 1:38 ` [PATCH v2 0/2] ufs: mcq: Share first hwq for dev comamnd and IO request Martin K. Petersen
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=20230610021553.1213-1-powen.kao@mediatek.com \
--to=powen.kao@mediatek.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=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®