All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanley Chu <stanley.chu@mediatek.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: <jejb@linux.ibm.com>, <linux-scsi@vger.kernel.org>,
	<alim.akhtar@samsung.com>, <asutoshd@codeaurora.org>,
	<avri.altman@wdc.com>, <chun-hung.wu@mediatek.com>,
	<kuohong.wang@mediatek.com>, <linux-mediatek@lists.infradead.org>,
	<peter.wang@mediatek.com>, <beanhuo@micron.com>,
	<matthias.bgg@gmail.com>, <andy.teng@mediatek.com>,
	<bvanassche@acm.org>, <cang@codeaurora.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/4] scsi: ufs: allow customizable WriteBooster flush policy
Date: Fri, 15 May 2020 09:15:58 +0800	[thread overview]
Message-ID: <1589505358.3197.101.camel@mtkswgap22> (raw)
In-Reply-To: <158950485295.8169.36549719949053326.b4-ty@oracle.com>

Hi Martin,

On Thu, 2020-05-14 at 21:10 -0400, Martin K. Petersen wrote:
> On Sat, 9 May 2020 17:37:12 +0800, Stanley Chu wrote:
> 
> > This patch set tries to allow vendors to modify the WriteBooster flush policy.
> > 
> > In the same time, collect all customizable parameters to an unified structure to make UFS driver more clean.
> > 
> > v1 -> v2:
> >   - Squash patch [3] and [4]
> >   - Remove a dummy "new line" in patch [3]
> >   - Fix commit message in patch [3]
> > 
> > [...]
> 
> Applied to 5.8/scsi-queue, thanks!
> 
> I had to combine patches 1 and 2. Otherwise you'd get compile
> failures due to the fields moving inside the struct.
> 
> [1/4] scsi: ufs: Introduce ufs_hba_variant_params to group customizable parameters
>       https://git.kernel.org/mkp/scsi/c/90b8491c0033
> [3/4] scsi: ufs: Customize flush threshold for WriteBooster
>       https://git.kernel.org/mkp/scsi/c/d14734ae3ae7
> [4/4] scsi: ufs-mediatek: Customize WriteBooster flush policy
>       https://git.kernel.org/mkp/scsi/c/f48b285ae658
> 

Thanks so much for helping the patch squash.

Thanks,
Stanley Chu

WARNING: multiple messages have this Message-ID (diff)
From: Stanley Chu <stanley.chu@mediatek.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: bvanassche@acm.org, linux-scsi@vger.kernel.org,
	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, beanhuo@micron.com,
	linux-arm-kernel@lists.infradead.org, asutoshd@codeaurora.org
Subject: Re: [PATCH v2 0/4] scsi: ufs: allow customizable WriteBooster flush policy
Date: Fri, 15 May 2020 09:15:58 +0800	[thread overview]
Message-ID: <1589505358.3197.101.camel@mtkswgap22> (raw)
In-Reply-To: <158950485295.8169.36549719949053326.b4-ty@oracle.com>

Hi Martin,

On Thu, 2020-05-14 at 21:10 -0400, Martin K. Petersen wrote:
> On Sat, 9 May 2020 17:37:12 +0800, Stanley Chu wrote:
> 
> > This patch set tries to allow vendors to modify the WriteBooster flush policy.
> > 
> > In the same time, collect all customizable parameters to an unified structure to make UFS driver more clean.
> > 
> > v1 -> v2:
> >   - Squash patch [3] and [4]
> >   - Remove a dummy "new line" in patch [3]
> >   - Fix commit message in patch [3]
> > 
> > [...]
> 
> Applied to 5.8/scsi-queue, thanks!
> 
> I had to combine patches 1 and 2. Otherwise you'd get compile
> failures due to the fields moving inside the struct.
> 
> [1/4] scsi: ufs: Introduce ufs_hba_variant_params to group customizable parameters
>       https://git.kernel.org/mkp/scsi/c/90b8491c0033
> [3/4] scsi: ufs: Customize flush threshold for WriteBooster
>       https://git.kernel.org/mkp/scsi/c/d14734ae3ae7
> [4/4] scsi: ufs-mediatek: Customize WriteBooster flush policy
>       https://git.kernel.org/mkp/scsi/c/f48b285ae658
> 

Thanks so much for helping the patch squash.

Thanks,
Stanley Chu
_______________________________________________
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: Stanley Chu <stanley.chu@mediatek.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: bvanassche@acm.org, linux-scsi@vger.kernel.org,
	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, beanhuo@micron.com,
	linux-arm-kernel@lists.infradead.org, asutoshd@codeaurora.org
Subject: Re: [PATCH v2 0/4] scsi: ufs: allow customizable WriteBooster flush policy
Date: Fri, 15 May 2020 09:15:58 +0800	[thread overview]
Message-ID: <1589505358.3197.101.camel@mtkswgap22> (raw)
In-Reply-To: <158950485295.8169.36549719949053326.b4-ty@oracle.com>

Hi Martin,

On Thu, 2020-05-14 at 21:10 -0400, Martin K. Petersen wrote:
> On Sat, 9 May 2020 17:37:12 +0800, Stanley Chu wrote:
> 
> > This patch set tries to allow vendors to modify the WriteBooster flush policy.
> > 
> > In the same time, collect all customizable parameters to an unified structure to make UFS driver more clean.
> > 
> > v1 -> v2:
> >   - Squash patch [3] and [4]
> >   - Remove a dummy "new line" in patch [3]
> >   - Fix commit message in patch [3]
> > 
> > [...]
> 
> Applied to 5.8/scsi-queue, thanks!
> 
> I had to combine patches 1 and 2. Otherwise you'd get compile
> failures due to the fields moving inside the struct.
> 
> [1/4] scsi: ufs: Introduce ufs_hba_variant_params to group customizable parameters
>       https://git.kernel.org/mkp/scsi/c/90b8491c0033
> [3/4] scsi: ufs: Customize flush threshold for WriteBooster
>       https://git.kernel.org/mkp/scsi/c/d14734ae3ae7
> [4/4] scsi: ufs-mediatek: Customize WriteBooster flush policy
>       https://git.kernel.org/mkp/scsi/c/f48b285ae658
> 

Thanks so much for helping the patch squash.

Thanks,
Stanley Chu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-15  1:16 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
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 [this message]
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=1589505358.3197.101.camel@mtkswgap22 \
    --to=stanley.chu@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=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=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=peter.wang@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.