linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bean Huo <huobean@gmail.com>
To: Can Guo <cang@codeaurora.org>
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com,
	asutoshd@codeaurora.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com, stanley.chu@mediatek.com,
	beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] scsi: ufs: change ufshcd_comp_devman_upiu() to ufshcd_compose_devman_upiu()
Date: Sat, 15 Aug 2020 12:37:37 +0200	[thread overview]
Message-ID: <b1081d95d115848d657bd48ca05f27ab0db01c7e.camel@gmail.com> (raw)
In-Reply-To: <ca175083f887ab0204f63002b5e2c4c7@codeaurora.org>

On Sat, 2020-08-15 at 09:52 +0800, Can Guo wrote:
> Hi Bean,
> 
> On 2020-08-14 17:50, Bean Huo wrote:
> > From: Bean Huo <beanhuo@micron.com>
> > 
> > ufshcd_comp_devman_upiu() alwasy make me confuse that it is a
> > request
> > completion calling function. Change it to
> > ufshcd_compose_devman_upiu().
> > 
> > Signed-off-by: Bean Huo <beanhuo@micron.com>
> > Acked-by: Avri Altman <avri.altman@wdc.com>
> 
> I gave my reviewed by tag in previous version, you missed it. Here it
> is
> 
> Reviewed-by: Can Guo <cang@codeaurora.org>

Can

nice, thanks.

Bean


  parent reply	other threads:[~2020-08-15 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  9:50 [PATCH v3 0/2] make UFS dev_cmd more readable Bean Huo
2020-08-14  9:50 ` [PATCH v3 1/2] scsi: ufs: change ufshcd_comp_devman_upiu() to ufshcd_compose_devman_upiu() Bean Huo
2020-08-14 16:37   ` Asutosh Das
     [not found]   ` <ca175083f887ab0204f63002b5e2c4c7@codeaurora.org>
2020-08-15 10:37     ` Bean Huo [this message]
2020-08-16  1:01   ` Stanley Chu
2020-08-14  9:50 ` [PATCH v3 2/2] scsi: ufs: remove several redundant goto statements Bean Huo
2020-08-14 16:54   ` Asutosh Das
2020-08-16  1:01   ` Stanley Chu
2020-08-18  3:11 ` [PATCH v3 0/2] make UFS dev_cmd more readable 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=b1081d95d115848d657bd48ca05f27ab0db01c7e.camel@gmail.com \
    --to=huobean@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.com \
    --cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).