From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Peter Wang" <peter.wang@mediatek.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Orson Zhai" <orsonzhai@gmail.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Bean Huo" <beanhuo@micron.com>,
"Ziqi Chen" <quic_ziqichen@quicinc.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Philipp Stanner" <pstanner@redhat.com>,
"Minwoo Im" <minwoo.im@samsung.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Eric Biggers" <ebiggers@google.com>
Subject: Re: [PATCH] scsi: ufs: Constify the third pwr_change_notify() argument
Date: Wed, 12 Feb 2025 22:25:24 -0500 [thread overview]
Message-ID: <yq134giv84k.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250212213838.1044917-1-bvanassche@acm.org> (Bart Van Assche's message of "Wed, 12 Feb 2025 13:38:02 -0800")
Bart,
> The third pwr_change_notify() argument is an input parameter. Make
> this explicit by declaring it 'const'.
Applied to 6.15/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-02-13 3:25 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 [this message]
2025-02-13 10:57 ` Peter Wang (王信友)
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=yq134giv84k.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.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=matthias.bgg@gmail.com \
--cc=minwoo.im@samsung.com \
--cc=orsonzhai@gmail.com \
--cc=peter.wang@mediatek.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