From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: Clock Regression in next-20150130 caused by cb75a8fcd14e
Date: Fri, 30 Jan 2015 21:31:05 -0800 [thread overview]
Message-ID: <20150131053105.GA20944@roeck-us.net> (raw)
In-Reply-To: <20150131010443.GE16250@atomide.com>
On Fri, Jan 30, 2015 at 05:04:44PM -0800, Tony Lindgren wrote:
> Hi all,
>
> Looks like commit cb75a8fcd14e ("clk: Add rate constraints to clocks")
> causes a regression on at least omaps where the serial console either
> does not show anything, or just prints garbage.
>
> Reverting cb75a8fcd14e makes things work again on next-20150130.
>
> Any ideas?
>
The patch seems to have some problems.
Also see http://www.spinics.net/lists/kernel/msg1916843.html.
Guenter
next prev parent reply other threads:[~2015-01-31 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 1:04 Clock Regression in next-20150130 caused by cb75a8fcd14e Tony Lindgren
2015-01-31 5:31 ` Guenter Roeck [this message]
2015-02-01 23:26 ` Mike Turquette
2015-02-02 16:18 ` Tony Lindgren
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=20150131053105.GA20944@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).