From: zhangfei <zhangfei.gao@linaro.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
baruch@tkos.co.il, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] i2c: designware: use module_platform_driver
Date: Wed, 19 Jun 2013 09:00:02 +0800 [thread overview]
Message-ID: <51C10292.9000906@linaro.org> (raw)
In-Reply-To: <20130618162711.GG7718@katana>
On 13-06-19 12:27 AM, Wolfram Sang wrote:
> On Tue, Jun 11, 2013 at 10:37:09AM +0800, Zhangfei Gao wrote:
>> Instead of use platform_driver_probe, use module_platform_driver
>> To support deferred probing
>> Also subsys_initcall may too early to auto set pinctl
>>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> CC: Baruch Siach <baruch@tkos.co.il>
>
> Basically OK, but please resend for 3.12, so we get enough testing
> before entering mainline. I am a bit anxious of side
> effects and 3.11 is too near.
>
Dear Wolfram,
Sorry for the silly question: How to be prepared for 3.12?
Do you mean there is specific git & branch, which I should rebase on?
linux-next.git is what I use now.
Thanks
next prev parent reply other threads:[~2013-06-19 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 2:37 [PATCH v3 0/2] support hisilicon i2c Zhangfei Gao
2013-06-11 2:37 ` [PATCH v3 1/2] i2c: designware: use module_platform_driver Zhangfei Gao
2013-06-18 16:27 ` Wolfram Sang
2013-06-19 1:00 ` zhangfei [this message]
2013-06-11 2:37 ` [PATCH v3 2/2] i2c: designware: add two optional property tx/rx-fifo-size Zhangfei Gao
[not found] ` <1370918230-24793-3-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-14 3:37 ` Baruch Siach
2013-06-18 16:22 ` Wolfram Sang
2013-06-19 0:37 ` zhangfei
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=51C10292.9000906@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=baruch@tkos.co.il \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dirk.brandewie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).