linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] clk: meson: Add clock controller
Date: Thu, 4 Jun 2015 16:07:17 -0700	[thread overview]
Message-ID: <20150604230717.GE8099@codeaurora.org> (raw)
In-Reply-To: <1433157235-17275-1-git-send-email-carlo@caione.org>

On 06/01, Carlo Caione wrote:
> From: Carlo Caione <carlo@endlessm.com>
> 
> This patchset introduces preliminary support for the clock controller
> found on Amlogic MesonX SoCs and enables it for the Meson8b.
> 
> DTS patches with support for Meson8b SoCs will follow.
> 

Did you want to send the dts changes through arm-soc? Do they
depend on the header file that is included here? clk-next is not
stable and shouldn't be pulled into other developer's trees, so
if we need some stable commit to give off to arm-soc for v4.2
we need to know soon. Or we can split the header file off into a
different patch and send it through both arm-soc and clk tree.

Otherwise the patches look good. I fixed up the __init markings
on some functions which were in the wrong place.

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

  parent reply	other threads:[~2015-06-04 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 11:13 [PATCH v3 0/3] clk: meson: Add clock controller Carlo Caione
2015-06-01 11:13 ` [PATCH v3 1/3] clk: meson: Add support for Meson " Carlo Caione
2015-06-01 11:13 ` [PATCH v3 2/3] clk: meson: Document bindings for Meson8b " Carlo Caione
2015-06-01 11:13 ` [PATCH v3 3/3] clk: meson8b: Add support for Meson8b clocks Carlo Caione
2015-06-04 23:07 ` Stephen Boyd [this message]
2015-06-05  7:37   ` [PATCH v3 0/3] clk: meson: Add clock controller Carlo Caione
2015-06-06  0:45     ` Stephen Boyd

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=20150604230717.GE8099@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 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).