From: bengt.g.jonsson@stericsson.com (Bengt Jonsson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] regulators: Update of ab8500 driver
Date: Wed, 24 Nov 2010 08:57:09 +0100 [thread overview]
Message-ID: <4CECC555.8060408@stericsson.com> (raw)
In-Reply-To: <20101123183833.GB19212@rakim.wolfsonmicro.main>
On 2010-11-23 19:38, Mark Brown wrote:
> On Tue, Nov 23, 2010 at 07:25:53PM +0100, Bengt Jonsson wrote:
>> This patch updates the driver with some bug fixes, support
>> for v2 hardware, support for regulator_count_voltages,
>> changes for reading the board config, added indexing of
>> the regulator array and added debug prints.
>
> This is a whole series of changes which don't seem terribly related to
> each other and aren't clearly described - please split this out into a
> patch series which clearly shows each individual change. For example,
> one change per bug fix, another adding v2 support, another adding count
> support and so on. As things stand it's very difficult to review your
> patch as it's not clear what each change is supposed to be doing or that
> bits haven't been missed from changes.
I will do that.
>
>> - ret = abx500_get_register_interruptible(info->dev, info->voltage_bank,
>> - info->voltage_reg,&value);
>> + ret = abx500_get_register_interruptible(info->dev,
>> + info->voltage_bank, info->voltage_reg,®val);
>
> In addition to what's noted above you also appear to have some renaming
> of variables and struct members plus some other stylistic changes which
> adds to the noise, again these should be split out for ease of review.
I will do that too.
>
>> + [AB8500_REGULATOR_INTCORE] = {
>> + .desc = {
>> + .name = "intcore",
>
> The previous way of listing the regulators with a macro seemed more
> immediately readable?
Removing the macros is just my suggestion. The disadvantage I see with
macros is that I need to read both the macro and the listing to see what
it really does. On the other hand, macros are probably more compact. If
it is ok, I will break out a patch with this change and put it in the
end of the patch stack. Then you can decide if you want it or not.
WARNING: multiple messages have this Message-ID (diff)
From: Bengt Jonsson <bengt.g.jonsson@stericsson.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linus WALLEIJ <linus.walleij@stericsson.com>
Subject: Re: [PATCH 2/3] regulators: Update of ab8500 driver
Date: Wed, 24 Nov 2010 08:57:09 +0100 [thread overview]
Message-ID: <4CECC555.8060408@stericsson.com> (raw)
In-Reply-To: <20101123183833.GB19212@rakim.wolfsonmicro.main>
On 2010-11-23 19:38, Mark Brown wrote:
> On Tue, Nov 23, 2010 at 07:25:53PM +0100, Bengt Jonsson wrote:
>> This patch updates the driver with some bug fixes, support
>> for v2 hardware, support for regulator_count_voltages,
>> changes for reading the board config, added indexing of
>> the regulator array and added debug prints.
>
> This is a whole series of changes which don't seem terribly related to
> each other and aren't clearly described - please split this out into a
> patch series which clearly shows each individual change. For example,
> one change per bug fix, another adding v2 support, another adding count
> support and so on. As things stand it's very difficult to review your
> patch as it's not clear what each change is supposed to be doing or that
> bits haven't been missed from changes.
I will do that.
>
>> - ret = abx500_get_register_interruptible(info->dev, info->voltage_bank,
>> - info->voltage_reg,&value);
>> + ret = abx500_get_register_interruptible(info->dev,
>> + info->voltage_bank, info->voltage_reg,®val);
>
> In addition to what's noted above you also appear to have some renaming
> of variables and struct members plus some other stylistic changes which
> adds to the noise, again these should be split out for ease of review.
I will do that too.
>
>> + [AB8500_REGULATOR_INTCORE] = {
>> + .desc = {
>> + .name = "intcore",
>
> The previous way of listing the regulators with a macro seemed more
> immediately readable?
Removing the macros is just my suggestion. The disadvantage I see with
macros is that I need to read both the macro and the listing to see what
it really does. On the other hand, macros are probably more compact. If
it is ok, I will break out a patch with this change and put it in the
end of the patch stack. Then you can decide if you want it or not.
next prev parent reply other threads:[~2010-11-24 7:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 18:25 [PATCH 0/3] regulators: Update of ab8500 driver Bengt Jonsson
2010-11-23 18:25 ` Bengt Jonsson
2010-11-23 18:25 ` [PATCH 1/3] mfd: Added new regulator_data pointer to ab8500 board configuration Bengt Jonsson
2010-11-23 18:25 ` Bengt Jonsson
2010-11-23 18:30 ` Mark Brown
2010-11-23 18:30 ` Mark Brown
2010-11-24 8:24 ` Bengt Jonsson
2010-11-24 8:24 ` Bengt Jonsson
2010-11-24 11:36 ` Mark Brown
2010-11-24 11:36 ` Mark Brown
2010-11-24 12:13 ` Bengt Jonsson
2010-11-24 12:13 ` Bengt Jonsson
2010-11-23 18:25 ` [PATCH 2/3] regulators: Update of ab8500 driver Bengt Jonsson
2010-11-23 18:25 ` Bengt Jonsson
2010-11-23 18:38 ` Mark Brown
2010-11-23 18:38 ` Mark Brown
2010-11-24 7:57 ` Bengt Jonsson [this message]
2010-11-24 7:57 ` Bengt Jonsson
2010-11-24 10:48 ` Mark Brown
2010-11-24 10:48 ` Mark Brown
2010-11-24 12:11 ` Bengt Jonsson
2010-11-24 12:11 ` Bengt Jonsson
2010-11-23 18:25 ` [PATCH 3/3] mach-ux500: Updated and added regulator board configuration in ab8500 Bengt Jonsson
2010-11-23 18:25 ` Bengt Jonsson
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=4CECC555.8060408@stericsson.com \
--to=bengt.g.jonsson@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.