From: Wolfram Sang <wsa@the-dreams.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simon Horman <horms+renesas@verge.net.au>,
linux-mmc <linux-mmc@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: More TMIO MMC variant. What is a preferred name?
Date: Wed, 22 Nov 2017 08:59:38 +0100 [thread overview]
Message-ID: <20171122075937.knc2soqu5axdufzy@ninjato> (raw)
In-Reply-To: <CAK7LNARpchnGL8ZGWcFs=bxmH2FK71Voyd5K1E6=3bHTjd-gyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
> If we use "tmio_mmc" prefix (like "dw_mmc"),
>
> # core
> obj-$(CONFIG_MMC_TMIO) += tmio_mmc.o
> # TMIO-builtin MMC
> obj-$(CONFIG_MMC_TMIO_TMIO) += tmio_mmc_tmio.o
> # Reneses
> obj-$(CONFIG_MMC_TMIO_SDHI) += tmio_mmc_sdhi.o
> # UniPhier
> obj-$(CONFIG_MMC_TMIO_UNIPHIER) += tmio_mmc_uniphier.o
>
>
> tmio_mmc_tmio.o is a crazy name, but the syntax is clear.
>
> The first "tmio_mmc" means the IP name
> (since we decide this is the right name)
>
> The second "tmio" is the platform name
> the comes from the TMIO MFD.
Also fine with me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-22 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 7:52 More TMIO MMC variant. What is a preferred name? Masahiro Yamada
2017-11-08 17:53 ` Wolfram Sang
2017-11-09 12:31 ` Masahiro Yamada
2017-11-20 20:11 ` Wolfram Sang
2017-11-21 11:32 ` Ulf Hansson
2017-11-21 20:01 ` Wolfram Sang
2017-11-21 20:14 ` Ulf Hansson
2017-11-22 1:16 ` Masahiro Yamada
2017-11-22 1:20 ` Masahiro Yamada
2017-11-22 7:59 ` Wolfram Sang [this message]
2017-11-22 13:22 ` Masahiro Yamada
2017-11-22 15:18 ` Ulf Hansson
2017-11-22 17:08 ` Wolfram Sang
2017-11-23 7:04 ` Ulf Hansson
2017-11-27 17:14 ` Wolfram Sang
2017-11-28 8:04 ` Masahiro Yamada
2017-12-08 14:59 ` Wolfram Sang
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=20171122075937.knc2soqu5axdufzy@ninjato \
--to=wsa@the-dreams.de \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yamada.masahiro@socionext.com \
--cc=yoshihiro.shimoda.uh@renesas.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