From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>
Subject: Re: [PATCH] gpio: mvebu: Remove initcall-based driver initialization
Date: Fri, 9 May 2014 10:08:48 -0300 [thread overview]
Message-ID: <20140509130848.GB764@arch.cereza> (raw)
In-Reply-To: <CACRpkdbXq_0C-d+uJ8yz8esHDvmY4A+MM8XE4G2TKFpbdKTBNw@mail.gmail.com>
On 09 May 11:09 AM, Linus Walleij wrote:
> On Thu, Apr 24, 2014 at 10:54 PM, Ezequiel Garcia
> <ezequiel.garcia@free-electrons.com> wrote:
>
> > There's no reason to use an initcall to initialize this driver,
> > and regular module_platform_driver() can be used instead.
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
>
> Has anyone tested this on real hardware? That is the only test that
> counts on initcalls as it happens.
>
Yup, tested on my mvebu boards, don't remember which one.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-05-09 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:54 [PATCH] gpio: mvebu: Remove initcall-based driver initialization Ezequiel Garcia
2014-04-25 10:01 ` Javier Martinez Canillas
2014-04-29 13:23 ` Jason Cooper
2014-05-09 9:09 ` Linus Walleij
2014-05-09 13:08 ` Ezequiel Garcia [this message]
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=20140509130848.GB764@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.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