public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org
Subject: Re: [GIT PULL][FOR REVIEW] Regulators: Bring the AB8500 into the 20th century
Date: Wed, 30 Jan 2013 10:57:34 +0800	[thread overview]
Message-ID: <20130130025726.GG4945@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130129164131.GN18212@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

On Tue, Jan 29, 2013 at 04:41:31PM +0000, Lee Jones wrote:

> If you'd like me to sent the patches to the MLs for a better review
> platform I can do, but I'd like to get permission before I go and
> start upsetting people.

> This branch contains 111 patches and has already gone though multiple
> cycles of fixing-up, squashing, splitting and revert removal.

So, some highlights from a quick scan through:

 - Most of the OF stuff needs to go, OF isn't just a dumping ground for
   typing in all the platform data with no thought about abstraction.
   Things like -input-microvolt for example, and the mode switching
   needs to be completely reworked.

 - Send the arch/arm stuff separately, supplies with NULL for the device
   are generally not a good sign though.

 - The -debug code looks like it's all NIH stuff, large chunks of it
   are reproducing stuff that's already there, it looks to have copies
   of all the data defining the regulators that must be duplicated in
   the regulator drivers themselves (which isn't a triumph) and the
   overwhelming bulk of it looks totally generic so it really shouldn't
   be in a driver.

 - I can't help but think this would get a lot less verbose with regmap,
   there's a lot of functions that .
   The no-bus support just merged would make that a lot easier.

 - dbx500-prcmu looks worrying, it appears to be replicating bits of the
   core regulator API for some unclear reason.

So probably no point in posting the series as-is.  I'd recommend
starting off by pulling out the core feature additions to the regulator
driver and the -ext driver, that should make things a lot smaller.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-01-30  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 16:41 [GIT PULL][FOR REVIEW] Regulators: Bring the AB8500 into the 20th century Lee Jones
2013-01-30  1:57 ` Mark Brown
2013-01-30  2:57 ` Mark Brown [this message]

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=20130130025726.GG4945@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox