From: Shawn Guo <shawnguo@kernel.org>
To: Bai Ping <b51503@freescale.com>
Cc: kernel@pengutronix.de, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH Resend] clk: imx: add 'is_prepared' clk_ops callback for pllv3 clk
Date: Wed, 25 Nov 2015 11:51:03 +0800 [thread overview]
Message-ID: <20151125035103.GF11999@tiger> (raw)
In-Reply-To: <1448381213-24349-1-git-send-email-b51503@freescale.com>
On Wed, Nov 25, 2015 at 12:06:53AM +0800, Bai Ping wrote:
> Add 'is_prepared' callback function for pllv3 type clk to make sure when
> the system is bootup, the unused clk is in a known state to match the
> prepare count info.
>
> Signed-off-by: Bai Ping <b51503@freescale.com>
> Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH Resend] clk: imx: add 'is_prepared' clk_ops callback for pllv3 clk
Date: Wed, 25 Nov 2015 11:51:03 +0800 [thread overview]
Message-ID: <20151125035103.GF11999@tiger> (raw)
In-Reply-To: <1448381213-24349-1-git-send-email-b51503@freescale.com>
On Wed, Nov 25, 2015 at 12:06:53AM +0800, Bai Ping wrote:
> Add 'is_prepared' callback function for pllv3 type clk to make sure when
> the system is bootup, the unused clk is in a known state to match the
> prepare count info.
>
> Signed-off-by: Bai Ping <b51503@freescale.com>
> Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
Applied, thanks.
next prev parent reply other threads:[~2015-11-25 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 16:06 [PATCH Resend] clk: imx: add 'is_prepared' clk_ops callback for pllv3 clk Bai Ping
2015-11-24 16:06 ` Bai Ping
2015-11-25 3:51 ` Shawn Guo [this message]
2015-11-25 3:51 ` 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=20151125035103.GF11999@tiger \
--to=shawnguo@kernel.org \
--cc=b51503@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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.