From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] mfd: update i2c driver for max8925
Date: Tue, 2 Feb 2010 20:44:47 -0500 [thread overview]
Message-ID: <771cded01002021744y52574cdl3baf36999909d210@mail.gmail.com> (raw)
In-Reply-To: <20100202151554.GC28139@sortiz.org>
On Tue, Feb 2, 2010 at 10:15 AM, Samuel Ortiz <sameo@linux.intel.com> wrote:
>> Yes, the code is not very clear. Now I use i2c_new_dummy() now. Now I
>> attache new patches now.
>>
>> Updates are in below.
>> 1. use i2c_new_dummy() to replace i2c_new_probed_device().
>> 2. add onkey driver
>> 3. remove unused i2c pointer in rtc driver
> Very good, I just have one last comment:
>
>
>> @@ -142,27 +138,28 @@ static int __devinit max8925_probe(struct i2c_client *client,
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?const struct i2c_device_id *id)
>> ?{
>> ? ? ? struct max8925_platform_data *pdata = client->dev.platform_data;
>> - ? ? struct max8925_chip *chip;
>> + ? ? static struct max8925_chip *chip;
> That no longer needs to be static.
> The rest of the code looks fine to me. Once you remove that static
> definition, and you add some comments explaining why you need those 3 i2c
> pointers, I'll merge it.
>
Thanks a lot. I update the patch. Now the fix is in below.
1. Remove static on max8925_chip.
2. Add more comments on using 3 i2c pointers.
Best Regards
Haojian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-mfd-update-i2c-driver-for-max8925.patch
Type: text/x-patch
Size: 3590 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100202/363c745d/attachment.bin>
next prev parent reply other threads:[~2010-02-03 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 11:07 [PATCH 1/4] mfd: update i2c driver for max8925 Haojian Zhuang
2010-01-29 19:54 ` Samuel Ortiz
2010-02-02 14:22 ` Haojian Zhuang
2010-02-02 15:15 ` Samuel Ortiz
2010-02-03 1:44 ` Haojian Zhuang [this message]
2010-02-05 9:06 ` Samuel Ortiz
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=771cded01002021744y52574cdl3baf36999909d210@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--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).