From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Ian Campbell <ijc@hellion.org.uk>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: axp20x: Add module alias
Date: Mon, 3 Aug 2015 11:48:02 +0200 [thread overview]
Message-ID: <20150803094802.GE2564@lukather> (raw)
In-Reply-To: <1438591909.3726.7.camel@tiscali.nl>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Mon, Aug 03, 2015 at 10:51:49AM +0200, Paul Bolle wrote:
> On za, 2015-08-01 at 18:13 +0100, Ian Campbell wrote:
> > This allows the module to be autoloaded.
> >
> > Together with 07949bf9c63c ("cpufreq: dt: allow driver to boot
> > automatically") this is sufficient to allow a modular kernel (such
> > as Debian's) to enable cpufreq on a Cubietruck.
>
> > --- a/drivers/regulator/axp20x-regulator.c
> > +++ b/drivers/regulator/axp20x-regulator.c
>
> > +MODULE_ALIAS("platform:axp20x-regulator");
>
> Should this eventually go into stable?
>
> The regulator driver for AXP20x was added in v3.16, so this patch could
> currently be relevant for the v3.18.y and v4.1.y trees. (In those trees
> the corresponding platform devices, which are needed to make this alias
> useful, appear to be present.)
>
> Same question for 07949bf9c63c ("cpufreq: dt: allow driver to boot
> automatically"), I guess.
Yes, it probably should.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-03 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438433404.18644.13.camel@debian.org>
2015-08-01 17:13 ` [PATCH v2] regulator: axp20x: Add module alias Ian Campbell
2015-08-03 8:51 ` Paul Bolle
2015-08-03 9:48 ` Maxime Ripard [this message]
2015-08-04 17:28 ` Mark Brown
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=20150803094802.GE2564@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=broonie@kernel.org \
--cc=ijc@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=pebolle@tiscali.nl \
--cc=wens@csie.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