From: Mark Brown <broonie@kernel.org>
To: Yingjoe Chen <yingjoe.chen@mediatek.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Henry Chen <henryc.chen@mediatek.com>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
eddie.huang@mediatek.com, linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] regulator: mt6397: convert to arch_initcall
Date: Tue, 5 Jan 2016 13:44:52 +0000 [thread overview]
Message-ID: <20160105134452.GE16023@sirena.org.uk> (raw)
In-Reply-To: <1450944643.30352.9.camel@mtksdaap41>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Thu, Dec 24, 2015 at 04:10:43PM +0800, Yingjoe Chen wrote:
> These changes are related to pinctrl init order patch. The related
> discussion is here:
> http://lists.infradead.org/pipermail/linux-mediatek/2015-December/003298.html
So this is just to cut down on probe deferrals? Sorry but as you'll see
from the discussion in that thread I'm really not enthusiastic about
taking such patches. Trying to use initcall ordering is a hack we're
moving towards removing, isn't very robust and makes it harder to
convince people that it's worth doing anything to really improve things.
> I think Henry use arch_initcall because that's what pinctrl patch was
> using. In this case, we should use subsys_initcall for all these.
But why? This sort of random unexplained level picking is part of the
problem...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-05 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:16 [PATCH] regulator: mt6397: convert to arch_initcall Henry Chen
2015-12-23 12:00 ` Mark Brown
2015-12-24 8:10 ` Yingjoe Chen
2016-01-05 13:44 ` Mark Brown [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=20160105134452.GE16023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=djkurtz@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=henryc.chen@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=sameo@linux.intel.com \
--cc=yingjoe.chen@mediatek.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