From: Linus Walleij <linus.walleij@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/04] ARM: shmobile: Initial r8a7791 SoC support
Date: Fri, 06 Sep 2013 16:21:23 +0000 [thread overview]
Message-ID: <CACRpkdb7QkqCmTMua1yJNJxSAWff=0f6a2SWkf6K9SqbW0BOVg@mail.gmail.com> (raw)
In-Reply-To: <20130904034557.12546.97503.sendpatchset@w520>
On Wed, Sep 4, 2013 at 5:45 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> From: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
(...)
> arch/arm/mach-shmobile/clock-r8a7791.c | 198 +++++++++++++++++++++++++
So what about starting afresh by letting this new SoC use the
generic clk framework in drivers/clk from day one instead of
adding another chunk of custom clk code to the kernel?
(There may be reasons for this, but I have to ask the
inevitable question.)
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-09-06 16:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 3:45 [PATCH 00/04] ARM: shmobile: Initial r8a7791 SoC and Koelsch board support Magnus Damm
2013-09-04 3:45 ` [PATCH 01/04] ARM: shmobile: Initial r8a7791 SoC support Magnus Damm
2013-09-06 16:21 ` Linus Walleij [this message]
2013-09-09 0:16 ` Simon Horman
2013-09-09 6:55 ` Linus Walleij
2013-09-09 7:37 ` Magnus Damm
2013-09-09 7:21 ` Magnus Damm
2013-09-09 7:45 ` Linus Walleij
2013-09-09 8:05 ` Magnus Damm
2013-09-09 9:15 ` Linus Walleij
2013-09-09 10:32 ` Magnus Damm
2013-09-18 17:20 ` Olof Johansson
2013-09-04 3:46 ` [PATCH 02/04] ARM: shmobile: r8a7791 SCIF support Magnus Damm
2013-09-06 16:27 ` Linus Walleij
2013-09-09 0:15 ` Simon Horman
2013-09-09 6:54 ` Linus Walleij
2013-09-09 7:09 ` Simon Horman
2013-09-09 7:28 ` Magnus Damm
2013-09-09 7:24 ` Magnus Damm
2013-09-04 3:46 ` [PATCH 03/04] ARM: shmobile: r8a7791 CMT support Magnus Damm
2013-09-04 3:46 ` [PATCH 04/04] ARM: shmobile: Koelsch support Magnus Damm
2013-09-04 8:38 ` [PATCH 00/04] ARM: shmobile: Initial r8a7791 SoC and Koelsch board support Simon Horman
2013-09-06 7:09 ` Simon Horman
2013-09-09 7:39 ` Magnus Damm
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='CACRpkdb7QkqCmTMua1yJNJxSAWff=0f6a2SWkf6K9SqbW0BOVg@mail.gmail.com' \
--to=linus.walleij@linaro.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).