From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org, Markus Pargmann <mpa@pengutronix.de>,
Mark Brown <broonie@linaro.org>
Subject: Re: OMAP4 SDP regression...
Date: Mon, 17 Mar 2014 18:35:07 -0700 [thread overview]
Message-ID: <20140318013507.GD30471@atomide.com> (raw)
In-Reply-To: <20140317233229.GP21483@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [140317 16:35]:
> There's been a couple of regressions on OMAP4430 SDP I've only recently
> noticed:
>
> http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=1597
>
> Configuring network interfaces... udhcpc (v1.9.1) started
> Sending discover...
> Sending discover...
> Sending discover...
> No lease, failing
> done.
>
> No link lights come up either. The hardware is fine because uboot manages
> to successfully tftp the kernel.
>
> It looks like it was working in -rc4+armsoc and -rc5+armsoc, but not
> -rc6+armsoc.
>
> From what I can see, nothing has changed in drivers/net/ethernet/micrel/
> since rc5.
>
> I've been through the delta from 3.14-rc5, and I don't see anything
> obvious. Any ideas? Known problem?
Seems like plain v3.14-rc6 fails for me while -rc5 works. Bisecting
points to:
66fda75f regulator: core: Replace direct ops->disable usage
Also verified that v3.14-rc6 with 66fda75f reverted also works.
Markus & Mark, any ideas?
Regards,
Tony
next prev parent reply other threads:[~2014-03-18 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 23:32 OMAP4 SDP regression Russell King - ARM Linux
2014-03-18 1:35 ` Tony Lindgren [this message]
2014-03-18 7:59 ` Markus Pargmann
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=20140318013507.GD30471@atomide.com \
--to=tony@atomide.com \
--cc=broonie@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mpa@pengutronix.de \
/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