From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clkdev: Don't print errors on probe defer
Date: Tue, 17 Jun 2014 23:48:06 +0100 [thread overview]
Message-ID: <20140617224805.GN23430@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140617223305.32686.15540@quantum>
On Tue, Jun 17, 2014 at 03:33:05PM -0700, Mike Turquette wrote:
> Quoting Stephen Boyd (2014-06-13 16:36:31)
> > This error message can spam the logs if you have lots of probe
> > deferals due to missing clocks. Just silence the error in this
> > case because the driver should try again later.
> >
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>
> Looks OK to me. Russell?
Looks fine to me too. Should I assume you're looking to take it?
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-17 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 23:36 [PATCH] clkdev: Don't print errors on probe defer Stephen Boyd
2014-06-17 22:33 ` Mike Turquette
2014-06-17 22:48 ` Russell King - ARM Linux [this message]
2014-06-18 17:24 ` Mike Turquette
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=20140617224805.GN23430@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).