mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Gabriel L. Somlo" <gsomlo@gmail.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Karol Gugala <kgugala@antmicro.com>,
	Mateusz Holenko <mholenko@antmicro.com>,
	Kamil Rakoczy <krakoczy@antmicro.com>,
	mdudek@internships.antmicro.com,
	Paul Mackerras <paulus@ozlabs.org>, Joel Stanley <joel@jms.id.au>,
	david.abdurachmanov@sifive.com,
	Florent Kermarrec <florent@enjoy-digital.fr>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v6 3/3] mmc: Add driver for LiteX's LiteSDCard interface
Date: Fri, 7 Jan 2022 19:12:43 +0900	[thread overview]
Message-ID: <YdgSG7t2eG9YzkaG@antec> (raw)
In-Reply-To: <CAMuHMdX2ujViu9GivVHtgAqC6AdiL3CvdJM58pVteJe9KdvdqQ@mail.gmail.com>

On Fri, Jan 07, 2022 at 10:36:12AM +0100, Geert Uytterhoeven wrote:
> Hi Gabriel,
> 
> On Thu, Jan 6, 2022 at 11:50 PM Gabriel L. Somlo <gsomlo@gmail.com> wrote:
> > On Thu, Jan 06, 2022 at 08:19:39PM +0200, Andy Shevchenko wrote:
> > > On Thu, Jan 6, 2022 at 7:48 PM Gabriel Somlo <gsomlo@gmail.com> wrote:
> > > >
> > > > LiteX (https://github.com/enjoy-digital/litex) is a SoC framework
> > > > that targets FPGAs. LiteSDCard is a small footprint, configurable
> > > > SDCard core commonly used in LiteX designs.
> > > >
> > > > The driver was first written in May 2020 and has been maintained
> > > > cooperatively by the LiteX community. Thanks to all contributors!
> > >
> > > > +config MMC_LITEX
> > > > +       tristate "LiteX MMC Host Controller support"
> > > > +       depends on OF
> > > > +       depends on PPC_MICROWATT || LITEX || COMPILE_TEST
> > > > +       help
> > > > +         This selects support for the MMC Host Controller found in LiteX SoCs.
> > > > +
> > > > +         If unsure, say N.
> > >
> > > What would be the module name if built as a module?
> >
> > litex_mmc.ko -- why are you asking? I.e., should I mention that anywhere
> > in the Kconfig blurb (I don't see other blurbs doing that, fwiw)?
> 
> Many (most?) blurbs do mention the module name.

I was doubting this as well, but I searched and its true.  The text 'module will
be called' shows up many times, there is also different text.

 $ grep -r 'module will be called' drivers/ | wc
   1347    9023   9086

 $ grep -r 'tristate \"' drivers/ | wc
   7169   47486  521795

So maybe >10% have module name in the blurb.  Example:

          To compile this driver as a module, choose M here: the
          module will be called tifm_sd.

Thanks,

-Stafford

  reply	other threads:[~2022-01-07 10:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 17:48 [PATCH v6 0/3] mmc: Add LiteSDCard mmc driver Gabriel Somlo
2022-01-06 17:48 ` [PATCH v6 1/3] MAINTAINERS: co-maintain LiteX platform Gabriel Somlo
2022-01-06 17:48 ` [PATCH v6 2/3] dt-bindings: mmc: Add bindings for LiteSDCard Gabriel Somlo
2022-01-06 17:48 ` [PATCH v6 3/3] mmc: Add driver for LiteX's LiteSDCard interface Gabriel Somlo
2022-01-06 18:19   ` Andy Shevchenko
2022-01-06 22:50     ` Gabriel L. Somlo
2022-01-07  9:36       ` Geert Uytterhoeven
2022-01-07 10:12         ` Stafford Horne [this message]
2022-01-07 10:24           ` Andy Shevchenko
2022-01-07 10:29             ` Geert Uytterhoeven
2022-01-07 10:30               ` Geert Uytterhoeven
2022-01-07 10:38                 ` Andy Shevchenko
2022-01-07 12:32             ` Stafford Horne
2022-01-07 14:07           ` Gabriel L. Somlo

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=YdgSG7t2eG9YzkaG@antec \
    --to=shorne@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=david.abdurachmanov@sifive.com \
    --cc=devicetree@vger.kernel.org \
    --cc=florent@enjoy-digital.fr \
    --cc=geert@linux-m68k.org \
    --cc=gsomlo@gmail.com \
    --cc=joel@jms.id.au \
    --cc=kgugala@antmicro.com \
    --cc=krakoczy@antmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mdudek@internships.antmicro.com \
    --cc=mholenko@antmicro.com \
    --cc=paulus@ozlabs.org \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=ulf.hansson@linaro.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

Powered by JetHome