From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Brownell <david-b@pacbell.net>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, lrg@slimlogic.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator core: fix double-free in regulator_register() error path
Date: Tue, 28 Apr 2009 09:16:46 +0100 [thread overview]
Message-ID: <20090428081646.GC20027@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200904272008.50268.david-b@pacbell.net>
On Mon, Apr 27, 2009 at 08:08:50PM -0700, David Brownell wrote:
> On Saturday 25 April 2009, Paul Walmsley wrote:
> > For the 3430SDP users out there, this patch also fixes the boot hang after
> > "regulator_init_complete: incomplete constraints, leaving VAUX3 on"
> > on that device.
> For the record, that "incomplete constraints" message is bogus.
> On that board, VAUX3 has a complete set of constraints: it may
> only emit 2.8V.
It's not VAUX3 that it's saying has incomplete constraints, it's the
board as a whole - if the constraints for the board were fully specified
(and the core had been told about it) then it would power off VAUX3 at
that point.
> Mark and/or Liam ... you might want to fix that diagnostic, to
> avoid leading more developers astray!
Probably shove a "board has" in there or something I guess.
next prev parent reply other threads:[~2009-04-28 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 11:28 [PATCH] regulator core: fix double-free in regulator_register() error path Paul Walmsley
2009-04-25 22:11 ` David Brownell
2009-04-26 4:53 ` Paul Walmsley
2009-04-28 3:08 ` David Brownell
2009-04-28 3:08 ` David Brownell
2009-04-28 8:16 ` Mark Brown [this message]
2009-04-28 9:32 ` David Brownell
2009-04-28 9:32 ` David Brownell
2009-04-28 11:00 ` Mark Brown
2009-04-28 11:47 ` David Brownell
2009-04-28 11:47 ` David Brownell
2009-04-28 12:47 ` Mark Brown
2009-04-26 9:23 ` Mark Brown
2009-04-27 11:40 ` Liam Girdwood
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=20090428081646.GC20027@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.com \
/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.