From: yong.shen@linaro.org (Yong Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] make mc13783 regulator code generic
Date: Thu, 2 Dec 2010 19:15:23 +0800 [thread overview]
Message-ID: <AANLkTinqk5U3HJX6BoceXH=QG2QtW8oVUkdPoVZdcQ4m@mail.gmail.com> (raw)
In-Reply-To: <20101202105701.GB26555@pengutronix.de>
Sorry, I will resend them.
2010/12/2 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> On Thu, Dec 02, 2010 at 06:45:32PM +0800, Yong Shen wrote:
>> Hi there,
>>
>> Please give comments inline and use attached patch for testing.
>>
>> Thanks
>> Yong
>>
>>
>> From 377c680c35089aea7697397c42349189843eeaff Mon Sep 17 00:00:00 2001
>> From: Yong Shen <yong.shen@linaro.org>
>> Date: Thu, 2 Dec 2010 14:59:00 +0800
>> Subject: [PATCH 2/2] make mc13783 regulator code generic
>>
>> move some common functions and micros of mc13783 regulaor driver to
> s/micros/macros/ s/regulaor/regulator/
>
>> a seperate file, which makes it possible for mc13892 to share code.
> s/seperate/separate/
>
> (Note I havn't looked at the patch)
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K. ? ? ? ? ? ? ? ? ? ? ? ? ? | Uwe Kleine-K?nig ? ? ? ? ? ?|
> Industrial Linux Solutions ? ? ? ? ? ? ? ? | http://www.pengutronix.de/ ?|
>
next prev parent reply other threads:[~2010-12-02 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 7:15 [PATCHv2] make mc13783 regulator code generic Yong Shen
2010-12-01 7:50 ` Sascha Hauer
2010-12-02 2:36 ` Yong Shen
2010-12-01 11:25 ` Mark Brown
2010-12-02 2:41 ` Yong Shen
2010-12-02 10:45 ` [PATCH 2/2] " Yong Shen
2010-12-02 10:57 ` Uwe Kleine-König
2010-12-02 11:15 ` Yong Shen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-02 6:59 Yong Shen
2010-12-02 6:59 Yong Shen
2010-12-02 11:20 Yong Shen
2010-12-02 17:37 ` 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='AANLkTinqk5U3HJX6BoceXH=QG2QtW8oVUkdPoVZdcQ4m@mail.gmail.com' \
--to=yong.shen@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).