From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
Cc: Stanley Chu <stanley.chu@mediatek.com>,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com,
beanhuo@micron.com, cang@codeaurora.org, matthias.bgg@gmail.com,
bvanassche@acm.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kuohong.wang@mediatek.com,
peter.wang@mediatek.com, chun-hung.wu@mediatek.com,
andy.teng@mediatek.com
Subject: Re: [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy
Date: Tue, 12 May 2020 12:21:47 -0400 [thread overview]
Message-ID: <yq1v9l115us.fsf@oracle.com> (raw)
In-Reply-To: <635f91f6-3a27-ffdd-4021-67705d4063fc@codeaurora.org> (Asutosh Das's message of "Mon, 11 May 2020 19:19:42 -0700")
Hi Asutosh!
> Patchset looks good to me.
>
> Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
When you want to approve an entire series, please respond to the cover
letter email. Otherwise the kernel.org tooling will only record the tag
for the individual patch you are responding to. In this case only patch
4 got tagged as reviewed in patchwork.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
andy.teng@mediatek.com, jejb@linux.ibm.com,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, avri.altman@wdc.com,
cang@codeaurora.org, linux-mediatek@lists.infradead.org,
peter.wang@mediatek.com, alim.akhtar@samsung.com,
matthias.bgg@gmail.com, Stanley Chu <stanley.chu@mediatek.com>,
bvanassche@acm.org, linux-arm-kernel@lists.infradead.org,
beanhuo@micron.com
Subject: Re: [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy
Date: Tue, 12 May 2020 12:21:47 -0400 [thread overview]
Message-ID: <yq1v9l115us.fsf@oracle.com> (raw)
In-Reply-To: <635f91f6-3a27-ffdd-4021-67705d4063fc@codeaurora.org> (Asutosh Das's message of "Mon, 11 May 2020 19:19:42 -0700")
Hi Asutosh!
> Patchset looks good to me.
>
> Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
When you want to approve an entire series, please respond to the cover
letter email. Otherwise the kernel.org tooling will only record the tag
for the individual patch you are responding to. In this case only patch
4 got tagged as reviewed in patchwork.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
andy.teng@mediatek.com, jejb@linux.ibm.com,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, avri.altman@wdc.com,
cang@codeaurora.org, linux-mediatek@lists.infradead.org,
peter.wang@mediatek.com, alim.akhtar@samsung.com,
matthias.bgg@gmail.com, Stanley Chu <stanley.chu@mediatek.com>,
bvanassche@acm.org, linux-arm-kernel@lists.infradead.org,
beanhuo@micron.com
Subject: Re: [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy
Date: Tue, 12 May 2020 12:21:47 -0400 [thread overview]
Message-ID: <yq1v9l115us.fsf@oracle.com> (raw)
In-Reply-To: <635f91f6-3a27-ffdd-4021-67705d4063fc@codeaurora.org> (Asutosh Das's message of "Mon, 11 May 2020 19:19:42 -0700")
Hi Asutosh!
> Patchset looks good to me.
>
> Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
When you want to approve an entire series, please respond to the cover
letter email. Otherwise the kernel.org tooling will only record the tag
for the individual patch you are responding to. In this case only patch
4 got tagged as reviewed in patchwork.
--
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
next prev parent reply other threads:[~2020-05-12 16:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 9:37 [PATCH v2 0/4] scsi: ufs: allow customizable WriteBooster flush policy Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` [PATCH v2 1/4] scsi: ufs: introduce ufs_hba_variant_params to collect customizable parameters Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` [PATCH v2 2/4] scsi: ufs-mediatek: change the way to use " Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` [PATCH v2 3/4] scsi: ufs: customize flush threshold for WriteBooster Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` [PATCH v2 4/4] scsi: ufs-mediatek: customize WriteBooster flush policy Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-09 9:37 ` Stanley Chu
2020-05-12 2:19 ` Asutosh Das (asd)
2020-05-12 2:19 ` Asutosh Das (asd)
2020-05-12 2:19 ` Asutosh Das (asd)
2020-05-12 16:21 ` Martin K. Petersen [this message]
2020-05-12 16:21 ` Martin K. Petersen
2020-05-12 16:21 ` Martin K. Petersen
2020-05-12 18:10 ` Asutosh Das (asd)
2020-05-12 18:10 ` Asutosh Das (asd)
2020-05-12 18:10 ` Asutosh Das (asd)
2020-05-15 1:10 ` [PATCH v2 0/4] scsi: ufs: allow customizable " Martin K. Petersen
2020-05-15 1:10 ` Martin K. Petersen
2020-05-15 1:10 ` Martin K. Petersen
2020-05-15 1:15 ` Stanley Chu
2020-05-15 1:15 ` Stanley Chu
2020-05-15 1:15 ` Stanley Chu
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=yq1v9l115us.fsf@oracle.com \
--to=martin.petersen@oracle.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=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.