From: Tony Lindgren <tony@atomide.com>
To: Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Clock Regression in next-20150130 caused by cb75a8fcd14e
Date: Fri, 30 Jan 2015 17:04:44 -0800 [thread overview]
Message-ID: <20150131010443.GE16250@atomide.com> (raw)
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?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Clock Regression in next-20150130 caused by cb75a8fcd14e
Date: Fri, 30 Jan 2015 17:04:44 -0800 [thread overview]
Message-ID: <20150131010443.GE16250@atomide.com> (raw)
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?
Regards,
Tony
next reply other threads:[~2015-01-31 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 1:04 Tony Lindgren [this message]
2015-01-31 1:04 ` Clock Regression in next-20150130 caused by cb75a8fcd14e Tony Lindgren
2015-01-31 5:31 ` Guenter Roeck
2015-01-31 5:31 ` Guenter Roeck
2015-02-01 23:26 ` Mike Turquette
2015-02-01 23:26 ` Mike Turquette
2015-02-02 16:18 ` Tony Lindgren
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=20150131010443.GE16250@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=tomeu.vizoso@collabora.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.