public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanley Chu <stanley.chu@mediatek.com>
To: Can Guo <cang@codeaurora.org>
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>,
	<martin.peter~sen@oracle.com>,
	<linux-mediatek@lists.infradead.org>, <peter.wang@mediatek.com>,
	<alim.akhtar@samsung.com>, <matthias.bgg@gmail.com>,
	<asutoshd@codeaurora.org>, <linux-arm-kernel@lists.infradead.org>,
	<beanhuo@micron.com>
Subject: Re: [PATCH v5 2/8] scsi: ufs: remove init_prefetch_data in struct ufs_hba
Date: Mon, 16 Mar 2020 15:08:07 +0800	[thread overview]
Message-ID: <1584342487.14250.11.camel@mtksdccf07> (raw)
In-Reply-To: <51fde835f4f03fcca6e83ba6d3579f2e@codeaurora.org>

Hi Can,

On Mon, 2020-03-16 at 14:25 +0800, Can Guo wrote:
> On 2020-03-16 11:42, Stanley Chu wrote:
> > Struct init_prefetch_data currently is used privately in
> > ufshcd_init_icc_levels(), thus it can be removed from struct ufs_hba.
> > 
> > Signed-off-by: Stanley Chu <stanley.chu@mediatek.com>
> > Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
> > Reviewed-by: Avri Altman <avri.altman@wdc.com>
> 
> Hi Stanley,
> 
> Earlier, I have one similar patch for this, but it does more than this.
> Please check the mail I just sent.
> 
> Thanks,
> Can Guo.

OK! Thanks to remind me this. Then I can drop this cleanup patch #2 in
its series to not conflict with your proposed one.

Thanks,
Stanley Chu



  reply	other threads:[~2020-03-16  7:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  3:42 [PATCH v5 0/8] scsi: ufs: some cleanups and make the delay for host enabling customizable Stanley Chu
2020-03-16  3:42 ` [PATCH v5 1/8] scsi: ufs: fix uninitialized tx_lanes in ufshcd_disable_tx_lcc() Stanley Chu
2020-03-16  3:42 ` [PATCH v5 2/8] scsi: ufs: remove init_prefetch_data in struct ufs_hba Stanley Chu
2020-03-16  6:25   ` Can Guo
2020-03-16  7:08     ` Stanley Chu [this message]
2020-03-16  7:09       ` Can Guo
2020-03-16  3:42 ` [PATCH v5 3/8] scsi: ufs: use an enum for host capabilities Stanley Chu
2020-03-16  3:42 ` [PATCH v5 4/8] scsi: ufs: introduce common delay function Stanley Chu
2020-03-16  3:42 ` [PATCH v5 5/8] scsi: ufs-mediatek: replace all delay places by " Stanley Chu
2020-03-16  3:42 ` [PATCH v5 6/8] scsi: ufs: allow customized delay for host enabling Stanley Chu
2020-03-16  3:42 ` [PATCH v5 7/8] scsi: ufs: make HCE polling more compact to improve initialization latency Stanley Chu
2020-03-16  6:34   ` Can Guo
2020-03-16  3:42 ` [PATCH v5 8/8] scsi: ufs-mediatek: customize the delay for host enabling 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=1584342487.14250.11.camel@mtksdccf07 \
    --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.peter~sen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox