From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Aubin Constans <aubin.constans@microchip.com>,
Ben Dooks <ben-linux@fluff.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Eugen Hristev <eugen.hristev@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
Haibo Chen <haibo.chen@nxp.com>, Hu Ziji <huziji@marvell.com>,
imx@lists.linux.dev, Jaehoon Chung <jh80.chung@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
Michal Simek <michal.simek@amd.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
s32@nxp.com, Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Viresh Kumar <vireshk@kernel.org>
Subject: Re: [PATCH 00/11] mmc: rename mmc_retune_* to mmc_host_retune_*
Date: Mon, 28 Apr 2025 18:52:20 +0200 [thread overview]
Message-ID: <aA-yRD3FX5Nr9ypK@shikoro> (raw)
In-Reply-To: <CAPDyKFqxHd85DsUH6eZVyoocTDrvwNu+wTLRBq-jUwDY+2iFTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Hi Ulf,
uuuh, I overlooked this mail, sorry!
> Sorry if my suggestion was unclear. I only had the MMC_CAP|CAP2_*
> related functions in mind. I think we should leave the mmc_retune*
> functions as is as they are not "can" functions.
I agree. I suggested that in my initial series, too.
> mmc_host_cmd23, mmc_host_done_complete, mmc_boot_partition_access,
> mmc_host_uhs. All in drivers/mmc/core/host.h
>
> According to your earlier renaming series, we should rename these function too:
> mmc_host_can_cmd23, mmc_host_can_done_complete,
> mmc_host_can_boot_partition, mmc_host_can_uhs
>
> Does this make sense to you?
I don't know these functions well, so you are probably right. I'll look
into it. One question: do you really suggest:
mmc_boot_partition_access -> mmc_host_can_boot_partition
or should it be:
mmc_boot_partition_access -> mmc_host_can_boot_partition_access
? I tend to think the first is better, just making sure.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-28 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 11:13 [PATCH 00/11] mmc: rename mmc_retune_* to mmc_host_retune_* Wolfram Sang
2025-04-25 11:14 ` [PATCH 11/11] mmc: rename mmc_retune_needed() to mmc_host_retune_needed() Wolfram Sang
2025-04-28 9:58 ` [PATCH 00/11] mmc: rename mmc_retune_* to mmc_host_retune_* Ulf Hansson
2025-04-28 16:52 ` Wolfram Sang [this message]
2025-04-29 9:16 ` Ulf Hansson
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=aA-yRD3FX5Nr9ypK@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=adrian.hunter@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aubin.constans@microchip.com \
--cc=ben-linux@fluff.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=eugen.hristev@linaro.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=huziji@marvell.com \
--cc=imx@lists.linux.dev \
--cc=jh80.chung@samsung.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nicolas.ferre@microchip.com \
--cc=patrice.chotard@foss.st.com \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vigneshr@ti.com \
--cc=vireshk@kernel.org \
/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