public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.30-rc3] regulator: regression fix
Date: Tue, 28 Apr 2009 11:49:38 +0100	[thread overview]
Message-ID: <20090428104938.GG14626@sirena.org.uk> (raw)
In-Reply-To: <200904280243.42927.david-b@pacbell.net>

On Tue, Apr 28, 2009 at 02:43:42AM -0700, David Brownell wrote:
> On Tuesday 28 April 2009, Mark Brown wrote:

> > The change you're making isn't relevant to what I suspect the actual
> > problem is (you didn't specify, I may be wrong here).

> Restoring the "else" fixed the logic flaw ...

I'm not sure the code ever worked for whatever it is you're doing with
it - it'd never have set a maximum voltage constraint.

> > The code that was being fixed was only even in -next for a relatively
> > brief period of time.

> This is the first time I've seen the "fix" though.  Recall that
> the code in question has been in use for several months now, while
> waiting to wend its way into mainline.  It might be useful to CC
> a few more folk on such "fix" patches.

The fix was nothing to do with the behaviour of fixed voltage regulators
- it was about restoring support for regulators without voltage
constraints.  The code looked like it was just one of the small
optimisations you're fond of, skipping the validity check since we just
set constraints which ought to be valid.

I should've pushed back harder on the obscure code in the first place.

      reply	other threads:[~2009-04-28 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  2:59 [patch 2.6.30-rc3] regulator: regression fix David Brownell
2009-04-28  8:38 ` Mark Brown
2009-04-28  9:43   ` David Brownell
2009-04-28 10:49     ` 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=20090428104938.GG14626@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    /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