From: Olof Johansson <olof@lixom.net>
To: Jonas Jensen <jonas.jensen@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
arm@kernel.org, linux@arm.linux.org.uk, arnd@arndb.de,
soren.brinkmann@xilinx.com, peter.crosthwaite@xilinx.com,
linux@roeck-us.net
Subject: Re: [PATCH v7 0/2] ARM: mach-moxart: add MOXA ART SoC support
Date: Sun, 22 Dec 2013 12:01:19 -0800 [thread overview]
Message-ID: <20131222200119.GH9144@quad.lixom.net> (raw)
In-Reply-To: <1387450064-6598-1-git-send-email-jonas.jensen@gmail.com>
On Thu, Dec 19, 2013 at 11:47:42AM +0100, Jonas Jensen wrote:
> The reason behind why fixed rate clock "ref12" couldn't be moved from
> .dtsi to .dts:
>
> There was nothing else in "clocks { .. }", the entire block was then
> deleted from .dtsi.
>
> If a skeleton "clocks { .. }" remain in .dtsi, the node can then be
> moved to .dts, and of_clk_get() works again.
>
> Changes since v6:
>
> 1. move fixed rate clock "ref12" from .dtsi to .dts
> 2. sort new entry alphabetically in arch/arm/Kconfig
> 3. rebase to next-20131219: arch/arm/Makefile arch/arm/Kconfig
>
> Applies to next-20131219
>
> Jonas Jensen (2):
> ARM: mach-moxart: add MOXA ART SoC platform files
> ARM: mach-moxart: add MOXA ART SoC device tree files
Please just send an incremental patch to fixup, I'm not going to rebuild
branches yet again because of a third version within a few hours when I've
already applied and dropped twice. :)
-Olof
prev parent reply other threads:[~2013-12-22 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 10:47 [PATCH v7 0/2] ARM: mach-moxart: add MOXA ART SoC support Jonas Jensen
2013-12-19 10:47 ` [PATCH v7 1/2] ARM: mach-moxart: add MOXA ART SoC platform files Jonas Jensen
2013-12-19 10:47 ` [PATCH v7 2/2] ARM: mach-moxart: add MOXA ART SoC device tree files Jonas Jensen
2013-12-20 22:08 ` Peter Crosthwaite
2013-12-22 20:01 ` Olof Johansson [this message]
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=20131222200119.GH9144@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jonas.jensen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=peter.crosthwaite@xilinx.com \
--cc=soren.brinkmann@xilinx.com \
/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