All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Anuj Aggarwal <anuj.aggarwal@ti.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 1/8] Regulator: Add TPS65023 regulator driver
Date: Sun, 09 Aug 2009 12:20:55 +0100	[thread overview]
Message-ID: <1249816855.11250.33.camel@vega> (raw)
In-Reply-To: <20090807155358.GI639@sirena.org.uk>

On Fri, 2009-08-07 at 16:53 +0100, Mark Brown wrote:
> On Fri, Aug 07, 2009 at 08:55:26PM +0530, Anuj Aggarwal wrote:
> 

> > +static const struct tps_info tps65023_regs[] = {
> > +	{
> > +	.name = "VDCDC1",
> > +	.min_uV =  800000,
> > +	.max_uV = 1600000,
> > +	.fixed = 0,

No need to add fixed = 0 in this array as compiler will do this for you.

> > +	.table_len = ARRAY_SIZE(VDCDC1_VSEL_table),
> > +	.table = VDCDC1_VSEL_table,
> > +	},
> 
> Indentation here is a bit non-standard - I'd expect either the {} around
> the elements to be in column 0 or another level of indentation for the
> fields.
> 
> > +	{
> > +	.name = "VDCDC2",
> > +	.min_uV =  3300000,
> > +	.max_uV = 3300000,
> > +	.fixed = 1,
> > +	.table_len = 0,
> > +	},
> 
> You could drop the fixed flag and just have fixed be inferred from
> min_uV == max_uV?
> 

To be honest I prefer having the fixed = 1 here. It stands out more and
imho keeps things simple. Also table_len could be omitted.

Thanks

Liam

  reply	other threads:[~2009-08-09 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 15:25 [PATCH 1/8] Regulator: Add TPS65023 regulator driver Anuj Aggarwal
2009-08-07 15:53 ` Mark Brown
2009-08-09 11:20   ` Liam Girdwood [this message]
2009-08-07 20:24 ` Felipe Balbi

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=1249816855.11250.33.camel@vega \
    --to=lrg@slimlogic.co.uk \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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.