public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "bvanassche@acm.org" <bvanassche@acm.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
	"ebiggers@google.com" <ebiggers@google.com>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"quic_ziqichen@quicinc.com" <quic_ziqichen@quicinc.com>,
	"pstanner@redhat.com" <pstanner@redhat.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
	"u.kleine-koenig@baylibre.com" <u.kleine-koenig@baylibre.com>,
	"krzk@kernel.org" <krzk@kernel.org>,
	"orsonzhai@gmail.com" <orsonzhai@gmail.com>,
	"minwoo.im@samsung.com" <minwoo.im@samsung.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>
Subject: Re: [PATCH] scsi: ufs: Constify the third pwr_change_notify() argument
Date: Thu, 13 Feb 2025 10:57:49 +0000	[thread overview]
Message-ID: <5ed2ecd7acdbd5d70c36cff6e823124550e53e28.camel@mediatek.com> (raw)
In-Reply-To: <20250212213838.1044917-1-bvanassche@acm.org>

On Wed, 2025-02-12 at 13:38 -0800, Bart Van Assche wrote:
> 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> The third pwr_change_notify() argument is an input parameter. Make
> this
> explicit by declaring it 'const'.
> 
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
>  drivers/ufs/core/ufshcd-priv.h  |  6 +++---
>  drivers/ufs/host/ufs-exynos.c   | 10 +++++-----
>  drivers/ufs/host/ufs-exynos.h   |  2 +-
>  drivers/ufs/host/ufs-hisi.c     |  6 +++---
>  drivers/ufs/host/ufs-mediatek.c | 10 +++++-----
>  drivers/ufs/host/ufs-qcom.c     |  2 +-
>  drivers/ufs/host/ufs-sprd.c     |  6 +++---
>  drivers/ufs/host/ufshcd-pci.c   |  2 +-
>  include/ufs/ufshcd.h            |  8 ++++----
>  9 files changed, 26 insertions(+), 26 deletions(-)
> 
> 

Reviewed-by: Peter Wang <peter.wang@mediatek.com>



  parent reply	other threads:[~2025-02-13 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 21:38 [PATCH] scsi: ufs: Constify the third pwr_change_notify() argument Bart Van Assche
2025-02-13  3:25 ` Martin K. Petersen
2025-02-13 10:57 ` Peter Wang (王信友) [this message]
2025-02-19  1:06 ` 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=5ed2ecd7acdbd5d70c36cff6e823124550e53e28.camel@mediatek.com \
    --to=peter.wang@mediatek.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=avri.altman@wdc.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=ebiggers@google.com \
    --cc=krzk@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=minwoo.im@samsung.com \
    --cc=orsonzhai@gmail.com \
    --cc=pstanner@redhat.com \
    --cc=quic_ziqichen@quicinc.com \
    --cc=u.kleine-koenig@baylibre.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