From: Mike Turquette <mturquette@linaro.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 01/10] clk: shmobile: sh73a0 common clock framework implementation
Date: Wed, 03 Sep 2014 05:40:44 +0000 [thread overview]
Message-ID: <20140903054044.5251.8814@quantum> (raw)
In-Reply-To: <1409649186-1046-2-git-send-email-ulrich.hecht+renesas@gmail.com>
Quoting Ulrich Hecht (2014-09-02 02:12:57)
> diff --git a/drivers/clk/shmobile/Makefile b/drivers/clk/shmobile/Makefile
> index 531d4f6..0c4fd11 100644
> --- a/drivers/clk/shmobile/Makefile
> +++ b/drivers/clk/shmobile/Makefile
> @@ -5,6 +5,7 @@ obj-$(CONFIG_ARCH_R8A7779) += clk-r8a7779.o
> obj-$(CONFIG_ARCH_R8A7790) += clk-rcar-gen2.o
> obj-$(CONFIG_ARCH_R8A7791) += clk-rcar-gen2.o
> obj-$(CONFIG_ARCH_R8A7794) += clk-rcar-gen2.o
> +obj-$(CONFIG_ARCH_SH73A0) += clk-sh73a0.o
> obj-$(CONFIG_ARCH_SHMOBILE_MULTI) += clk-div6.o
> obj-$(CONFIG_ARCH_SHMOBILE_MULTI) += clk-mstp.o
> # for emply built-in.o
So I don't have any of the CONFIG_ARCH_R8A7794 stuff in my tree, per
this email thread [0].
Do you want the clk patches in this series to go through Simon's tree
also?
Regards,
Mike
[0] http://lkml.kernel.org/r/<20140826234307.GC9189@verge.net.au>
next prev parent reply other threads:[~2014-09-03 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 9:12 [PATCH v2 01/10] clk: shmobile: sh73a0 common clock framework implementation Ulrich Hecht
2014-09-03 5:40 ` Mike Turquette [this message]
2014-09-03 7:50 ` Ulrich Hecht
2014-09-04 6:49 ` Simon Horman
2014-09-04 7:13 ` Simon Horman
2014-09-09 20:46 ` Laurent Pinchart
2014-09-09 21:16 ` Laurent Pinchart
2014-09-09 21:24 ` Laurent Pinchart
2014-09-09 22:19 ` Mike Turquette
2014-09-09 22:27 ` Laurent Pinchart
2014-09-10 0:05 ` Simon Horman
2014-09-10 16:59 ` Mike Turquette
2014-09-12 8:50 ` Ulrich Hecht
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=20140903054044.5251.8814@quantum \
--to=mturquette@linaro.org \
--cc=linux-sh@vger.kernel.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).