From: Stephen Boyd <sboyd@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Carlo Caione <carlo@endlessm.com>,
linux-clk@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] clk: meson: add some error handling in meson_clk_register_cpu()
Date: Thu, 11 Jun 2015 16:13:25 -0700 [thread overview]
Message-ID: <20150611231325.GH29640@codeaurora.org> (raw)
In-Reply-To: <20150611152046.GG12192@mwanda>
On 06/11, Dan Carpenter wrote:
> This error handling hopefully isn't needed but it make the static
> checkers happy.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-06-11 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 15:20 [patch] clk: meson: add some error handling in meson_clk_register_cpu() Dan Carpenter
2015-06-11 15:26 ` Carlo Caione
2015-06-11 23:13 ` Stephen Boyd [this message]
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=20150611231325.GH29640@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=carlo@endlessm.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@linaro.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).