All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Timo Alho <talho@nvidia.com>,
	linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] clk: tegra: check BPMP response return code
Date: Sat, 21 Oct 2017 07:10:38 -0700	[thread overview]
Message-ID: <20171021141038.GB15990@codeaurora.org> (raw)
In-Reply-To: <20171017103736.GA30589@ulmo>

On 10/17, Thierry Reding wrote:
> On Thu, Sep 07, 2017 at 12:31:02PM +0300, Timo Alho wrote:
> > Check return code in BPMP response message(s). The typical error case
> > is when clock operation is attempted with invalid clock identifier.
> > 
> > Also remove error print from call to clk_get_info() as the
> > implementation loops through range of all possible identifier, but the
> > operation is expected error out when the clock id is unused.
> > 
> > Signed-off-by: Timo Alho <talho@nvidia.com>
> > ---
> >  drivers/clk/tegra/clk-bpmp.c | 15 ++++++++++-----
> >  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> Hi Mike, Stephen,
> 
> do you mind if I pick this up into the Tegra tree? It has a build
> dependency on patch 1/4.
> 
> I only now realized that you guys weren't on Cc, hence quoting in
> full.
> 

No worries

Acked-by: Stephen Boyd <sboyd@codeaurora.org>


-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-10-21 14:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  9:31 [PATCH 0/4] firmware: tegra: add checks for BPMP error return code Timo Alho
2017-09-07  9:31 ` Timo Alho
     [not found] ` <cover.1504776489.git.talho-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-09-07  9:31   ` [PATCH 1/4] firmware: tegra: propagate error code to caller Timo Alho
2017-09-07  9:31     ` Timo Alho
     [not found]     ` <c349d38a8cb1d00a4dc11d6aa286fb392017bc8c.1504776489.git.talho-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-09-21 11:19       ` Jon Hunter
2017-09-21 11:19         ` Jon Hunter
2017-10-17 10:41       ` Thierry Reding
2017-10-17 10:41         ` Thierry Reding
2017-09-07  9:31   ` [PATCH 2/4] clk: tegra: check BPMP response return code Timo Alho
2017-09-07  9:31     ` Timo Alho
2017-09-21 11:21     ` Jon Hunter
2017-09-21 11:21       ` Jon Hunter
     [not found]       ` <388e07bc-b7b4-cc17-026a-bd08d77942ca-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-09-29 13:46         ` Timo Alho
2017-09-29 13:46           ` Timo Alho
2017-09-29 14:53           ` Jon Hunter
     [not found]             ` <5dfbbc6d-0dc0-7d92-0bff-8b05ddd272b3-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-02  8:43               ` Timo Alho
2017-10-02  8:43                 ` Timo Alho
2017-10-02 20:23                 ` Jon Hunter
2017-10-17 10:37     ` Thierry Reding
2017-10-21 14:10       ` Stephen Boyd [this message]
2017-09-07  9:31   ` [PATCH 3/4] reset: " Timo Alho
2017-09-07  9:31     ` Timo Alho
     [not found]     ` <00e7714871d7568e9fc848dc5f76d14e07984a1e.1504776489.git.talho-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-02 20:24       ` Jon Hunter
2017-10-02 20:24         ` Jon Hunter
2017-10-17 10:40     ` Thierry Reding
2017-10-17 10:52       ` Philipp Zabel
2017-10-17 10:52         ` Philipp Zabel
     [not found]         ` <1508237537.6854.8.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-10-17 11:49           ` Thierry Reding
2017-10-17 11:49             ` Thierry Reding
2017-09-07  9:31 ` [PATCH 4/4] soc/tegra: bpmp: " Timo Alho
2017-09-07  9:31   ` Timo Alho
     [not found]   ` <8be4357544ffb9a60e116bc0a666189b93951c91.1504776489.git.talho-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-02 20:26     ` Jon Hunter
2017-10-02 20:26       ` Jon Hunter
2017-10-17 10:41   ` Thierry Reding

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=20171021141038.GB15990@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=talho@nvidia.com \
    --cc=thierry.reding@gmail.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.