[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <771cded01001260351w21af1448q9439fad3821c3c55@mail.gmail.com>
Date: Tue, 26 Jan 2010 06:51:59 -0500
From: Haojian Zhuang <haojian.zhuang@...il.com>
To: Liam Girdwood <lrg@...mlogic.co.uk>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/01] regulator: support max8649
On Tue, Jan 26, 2010 at 6:01 AM, Liam Girdwood <lrg@...mlogic.co.uk> wrote:
> On Tue, 2010-01-26 at 01:26 -0500, Haojian Zhuang wrote:
>> From 2b5a73c336d2b5dc48c8cf1f2a804b6968659f78 Mon Sep 17 00:00:00 2001
>> From: Haojian Zhuang <haojian.zhuang@...vell.com>
>> Date: Mon, 25 Jan 2010 10:24:09 -0500
>> Subject: [PATCH] regulator: enable max8649 regulator driver
>>
>> Signed-off-by: Haojian Zhuang <haojian.zhuang@...vell.com>
>
> Can you confirm all the changes compared to the last version.
>
Yes, exactly.
>> +static int max8649_get_voltage(struct regulator_dev *rdev)
>> +{
>> + struct max8649_regulator_info *info = rdev_get_drvdata(rdev);
>> + unsigned char data;
>> + int ret;
>> +
>> + ret = max8649_reg_read(info->i2c, info->vol_reg);
>> + if (ret < 0)
>> + return ret;
>> + data = (unsigned char)ret & MAX8649_VOL_MASK;
>> + return (max8649_list_voltage(rdev, data));
>
> Any reason why we have extra () here ?
>
Fixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists