From: Stephen Boyd <sboyd@codeaurora.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Gerhard Sittig <gsi@denx.de>
Subject: Re: [PATCH] powerpc/512x: clk: Remove CLK_IS_ROOT
Date: Wed, 1 Jun 2016 14:51:50 -0700 [thread overview]
Message-ID: <20160601215150.GB28218@codeaurora.org> (raw)
In-Reply-To: <1461115872-31722-1-git-send-email-sboyd@codeaurora.org>
On 04/19, Stephen Boyd wrote:
> This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate
> CLK_IS_ROOT", 2016-02-02) so remove it.
>
> Cc: Gerhard Sittig <gsi@denx.de>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Applied to clk-fixes
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-06-01 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 1:31 [PATCH] powerpc/512x: clk: Remove CLK_IS_ROOT Stephen Boyd
2016-06-01 21:51 ` 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=20160601215150.GB28218@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agust@denx.de \
--cc=gsi@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).