All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Bai Ping <b51503@freescale.com>
Cc: shawnguo@kernel.org, kernel@pengutronix.de,
	mturquette@baylibre.com, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: imx: Replace clk error check with imx_check_clocks()
Date: Mon, 30 Nov 2015 16:36:26 -0800	[thread overview]
Message-ID: <20151201003626.GB17532@codeaurora.org> (raw)
In-Reply-To: <1448504323-17737-1-git-send-email-b51503@freescale.com>

On 11/26, Bai Ping wrote:
> As we already have a 'imx_check_clocks' to do the clock error
> check, so cleanup the error check code.
> 
> Signed-off-by: Bai Ping <b51503@freescale.com>
> ---

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

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

WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: imx: Replace clk error check with imx_check_clocks()
Date: Mon, 30 Nov 2015 16:36:26 -0800	[thread overview]
Message-ID: <20151201003626.GB17532@codeaurora.org> (raw)
In-Reply-To: <1448504323-17737-1-git-send-email-b51503@freescale.com>

On 11/26, Bai Ping wrote:
> As we already have a 'imx_check_clocks' to do the clock error
> check, so cleanup the error check code.
> 
> Signed-off-by: Bai Ping <b51503@freescale.com>
> ---

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:[~2015-12-01  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  2:18 [PATCH] clk: imx: Replace clk error check with imx_check_clocks() Bai Ping
2015-11-26  2:18 ` Bai Ping
2015-12-01  0:36 ` Stephen Boyd [this message]
2015-12-01  0:36   ` Stephen Boyd
2015-12-02  6:11 ` Shawn Guo
2015-12-02  6:11   ` Shawn Guo

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=20151201003626.GB17532@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=b51503@freescale.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=shawnguo@kernel.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 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.