From: Wolfram Sang <wsa@the-dreams.de>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Fabio Porcedda <fabio.porcedda@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Libo Chen <libo.chen@huawei.com>,
linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@linaro.org,
linaro-kernel@lists.linaro.org, linaro-acpi@lists.linaro.org
Subject: Re: [PATCH 1/4] driver core: introduce helper macro initcall_driver()
Date: Mon, 30 Sep 2013 12:15:00 +0200 [thread overview]
Message-ID: <20130930101500.GA3222@katana> (raw)
In-Reply-To: <1380518035-5319-2-git-send-email-hanjun.guo@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Mon, Sep 30, 2013 at 01:13:52PM +0800, Hanjun Guo wrote:
> For some devices especially on platform/I2C/SPI bus, they want to
> be initialized earlier than other devices, so the driver use initcall
> such as subsys_initcall to make this device initialize earlier.
And this is something we want to get rid of in favor of deferred
probing.
>
> But for those drivers, lots of them just do nothing special in
> xxx_initcall/exit, so introduce a helper macro initcall_driver() to
> eliminate lots of boilerplate just like module_driver() did.
>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
So, NACK because using some *_initcall in drivers should not be
encouraged.
Thanks,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-30 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380518035-5319-1-git-send-email-hanjun.guo@linaro.org>
[not found] ` <1380518035-5319-2-git-send-email-hanjun.guo@linaro.org>
2013-09-30 9:16 ` [PATCH 1/4] driver core: introduce helper macro initcall_driver() Mark Brown
2013-09-30 14:23 ` Hanjun Guo
2013-09-30 10:15 ` Wolfram Sang [this message]
2013-09-30 14:28 ` Hanjun Guo
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=20130930101500.GA3222@katana \
--to=wsa@the-dreams.de \
--cc=broonie@kernel.org \
--cc=fabio.porcedda@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hanjun.guo@linaro.org \
--cc=libo.chen@huawei.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rafael.j.wysocki@intel.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