devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: takasi-y@ops.dti.ne.jp, SH-Linux <linux-sh@vger.kernel.org>,
	Ben Dooks <ben.dooks@codethink.co.uk>,
	Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>,
	Mike Turquette <mturquette@linaro.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	devicetree@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] ARM: shmobile: emev2: Add clock tree description in DT
Date: Wed, 9 Oct 2013 12:40:12 +0900	[thread overview]
Message-ID: <20131009034011.GN15065@verge.net.au> (raw)
In-Reply-To: <CANqRtoT0EYcn6U_-Zin7eryiYGwb0C16AyLXtnsQ0Srt1PTG=w@mail.gmail.com>

On Tue, Oct 08, 2013 at 02:54:26PM +0900, Magnus Damm wrote:
> On Tue, Oct 8, 2013 at 2:33 PM,  <takasi-y@ops.dti.ne.jp> wrote:
> > Add minimum clock tree description to .dts file.
> > This provides same set of clocks as current sh-clkfwk version .c
> > code does.
> >
> > Signed-off-by: Takashi Yoshii <takasi-y@ops.dti.ne.jp>

Thanks.

I plan to add this patch to a new topic branch,
topic/emev2-common-clock, in the renesas tree and
queue it up from there for inclusion in mainline
if/when the first patch of this series is accepted
by Mike Turquette.

  reply	other threads:[~2013-10-09  3:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  5:30 [PATCH v2 0/3] ARM: shmobile: kzm9d: migrate to common clock framework with DT takasi-y
2013-10-08  5:32 ` [PATCH v2 1/3] clk: emev2: Add support for emev2 SMU clocks " takasi-y
2013-10-08  5:58   ` Magnus Damm
2013-10-09  3:38     ` Simon Horman
     [not found]       ` <20131009033807.GM15065-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-10-09  6:10         ` Ben Dooks
2013-10-08  5:33 ` [PATCH v2 2/3] ARM: shmobile: emev2: Add clock tree description in DT takasi-y
2013-10-08  5:54   ` Magnus Damm
2013-10-09  3:40     ` Simon Horman [this message]
2013-10-08  5:34 ` [PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework takasi-y
2013-10-08  5:52   ` Magnus Damm
2013-10-09  3:40   ` Simon Horman
2013-10-09  4:59     ` Magnus Damm
2013-10-09  6:54       ` Simon Horman
2013-10-09  7:29         ` Magnus Damm
2013-10-09 10:39           ` Simon Horman
2013-10-29  4:42             ` Simon Horman
     [not found]               ` <20131029044239.GC20432-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-12-02  2:25                 ` Simon Horman
2013-12-23  6:41                   ` Mike Turquette
2013-12-23  8:00                     ` Simon Horman
2014-01-06  8:10                       ` Simon Horman

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=20131009034011.GN15065@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ben.dooks@codethink.co.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@linaro.org \
    --cc=shinya.kuribayashi.px@renesas.com \
    --cc=takasi-y@ops.dti.ne.jp \
    /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).