From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/9] clk: berlin: move to a dedicated sub-node
Date: Thu, 14 May 2015 18:12:25 -0700 [thread overview]
Message-ID: <20150515011225.GG31753@codeaurora.org> (raw)
In-Reply-To: <1428417909-27378-2-git-send-email-antoine.tenart@free-electrons.com>
On 04/07, Antoine Tenart wrote:
> The Berlin clock driver was sharing a DT node with the pin controller
> and the reset driver. All these devices are now sub-nodes of the chip
> controller. This patch rework the Berlin clock driver to allow moving
> the Berlin clock DT bindings into their own sub-node of the chip
> controller node.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.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: Stephen Boyd <sboyd@codeaurora.org>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: sebastian.hesselbarth@gmail.com, mturquette@linaro.org,
zmxu@marvell.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/9] clk: berlin: move to a dedicated sub-node
Date: Thu, 14 May 2015 18:12:25 -0700 [thread overview]
Message-ID: <20150515011225.GG31753@codeaurora.org> (raw)
In-Reply-To: <1428417909-27378-2-git-send-email-antoine.tenart@free-electrons.com>
On 04/07, Antoine Tenart wrote:
> The Berlin clock driver was sharing a DT node with the pin controller
> and the reset driver. All these devices are now sub-nodes of the chip
> controller. This patch rework the Berlin clock driver to allow moving
> the Berlin clock DT bindings into their own sub-node of the chip
> controller node.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-05-15 1:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 14:45 [PATCH v3 0/9] ARM: berlin: refactor the clock Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 1/9] clk: berlin: move to a dedicated sub-node Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-28 11:32 ` Sebastian Hesselbarth
2015-04-28 11:32 ` Sebastian Hesselbarth
2015-05-07 8:46 ` Sebastian Hesselbarth
2015-05-07 8:46 ` Sebastian Hesselbarth
2015-05-15 1:12 ` Stephen Boyd [this message]
2015-05-15 1:12 ` Stephen Boyd
2015-04-07 14:45 ` [PATCH v3 2/9] Documentation: bindings: move the Berlin clock documentation Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-05-15 1:13 ` Stephen Boyd
2015-05-15 1:13 ` Stephen Boyd
2015-04-07 14:45 ` [PATCH v3 3/9] ARM: berlin: rework the clock node for BG2 Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 4/9] ARM: berlin: rework the clock node for BG2CD Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 5/9] ARM: berlin: rework the clock node for BG2Q Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 6/9] Documentation: bindings: update the berlin chip and system ctrl doc Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 7/9] ARM: berlin: remove useless chip and system ctrl compatibles in BG2 Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 8/9] ARM: berlin: remove useless chip and system ctrl compatibles in BG2CD Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
2015-04-07 14:45 ` [PATCH v3 9/9] ARM: berlin: remove useless chip and system ctrl compatibles in BG2Q Antoine Tenart
2015-04-07 14:45 ` Antoine Tenart
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=20150515011225.GG31753@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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.