From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
lrg@ti.com, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Board breakage due to upstream patch
Date: Thu, 29 Mar 2012 12:53:31 +0100 [thread overview]
Message-ID: <4F744D3B.3030605@linaro.org> (raw)
In-Reply-To: <20120329110424.GD3668@opensource.wolfsonmicro.com>
On 29/03/12 12:04, Mark Brown wrote:
> On Thu, Mar 29, 2012 at 10:52:07AM +0100, Lee Jones wrote:
>
>> Your patch "regulator: Support driver probe deferral" (below) prevents my Snowball Development Board from booting.
>
>> What's the correct thing to do?
>
> Provide a report with a little more detail on the problem:
>
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
>
> It's possible the patch I posted yesterday which fixes a deadlock in
> error handling paths might help, though given that all we're doing is
> changing the error code here I'd say regulator support on your your
> board was broken anyway. Given the lack of any detail in your report
> I'm just guessing completely in the dark here.
I haven't undertaken any debugging of the issue, as I don't have the
time, nor do I have the knowledge to be able to tell you what might be
happening as a result of the change.
All I can tell you at this stage is that with your patch applied, my
board doesn't boot past "Uncompressing Linux... done, booting the
kernel..". Once reverted it boots again.
I'll try to find some time to have a dig around, in order to provide you
with some more useful information.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2012-03-29 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 9:52 Board breakage due to upstream patch Lee Jones
2012-03-29 11:04 ` Mark Brown
2012-03-29 11:53 ` Lee Jones [this message]
2012-03-29 12:05 ` Mark Brown
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=4F744D3B.3030605@linaro.org \
--to=lee.jones@linaro.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox