From: Arnd Bergmann <arnd@arndb.de>
To: Josh Cartwright <josh.cartwright@ni.com>
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
John Linn <john.linn@xilinx.com>,
Nick Bowler <nbowler@elliptictech.com>
Subject: Re: [PATCH v3 0/5] zynq subarch cleanups
Date: Wed, 24 Oct 2012 12:09:58 +0000 [thread overview]
Message-ID: <201210241209.58655.arnd@arndb.de> (raw)
In-Reply-To: <20121024003218.GA31625@beefymiracle.amer.corp.natinst.com>
On Wednesday 24 October 2012, Josh Cartwright wrote:
> Things have been relatively quiet on the Zynq front lately. This patchset does
> a bit of cleanup of the Zynq subarchitecture. It was the necessary set of
> things I had to do to get a zynq target booting with the upstream qemu model.
>
> Patches 1 and 2 move zynq to use the GIC and pl310 L2 cache controller device
> tree mappings respectively.
>
> Patch 3 removes unused clock infrastructure. the plan is to rework the
> out-of-tree Xilinx generic clk support into something suitable for merging.
> What's in tree now just isn't used at all, and can be removed.
>
> Patch 4 and 5 move around the static peripheral mappings into the vmalloc area.
Looks all good to me now.
>
> I intentionally did not Cc stable on patch 5, even though you had
> suggested otherwise. I do not think it will apply cleanly to the stable
> trees independent of the other patches. Additionally, with the current
> state of zynq upstream, I'm not convinced there would be enough users to
> make it worth the effort.
Ok, fair enough.
> Additionally, I've left the SCU static mapping around, even though its
> currently unused. We'll eventually need it around (maybe in a different form)
> when SMP support is added.
Right.
John, are you going to pick up these patches and send a pull request?
Arnd
prev parent reply other threads:[~2012-10-24 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 0:32 [PATCH v3 0/5] zynq subarch cleanups Josh Cartwright
2012-10-24 0:33 ` [PATCH v3 1/5] zynq: use GIC device tree bindings Josh Cartwright
2012-10-24 12:03 ` Arnd Bergmann
2012-10-24 0:34 ` [PATCH v3 2/5] zynq: use pl310 " Josh Cartwright
2012-10-24 12:04 ` Arnd Bergmann
2012-10-24 0:34 ` [PATCH v3 3/5] zynq: remove use of CLKDEV_LOOKUP Josh Cartwright
2012-10-24 12:05 ` Arnd Bergmann
2012-10-24 13:32 ` Nick Bowler
2012-10-24 18:16 ` Josh Cartwright
2012-10-24 0:35 ` [PATCH v3 4/5] ARM: annotate VMALLOC_END definition with _AC Josh Cartwright
2012-10-24 12:07 ` Arnd Bergmann
2012-10-24 0:35 ` [PATCH v3 5/5] zynq: move static peripheral mappings Josh Cartwright
2012-10-24 12:08 ` Arnd Bergmann
2012-10-24 12:09 ` Arnd Bergmann [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=201210241209.58655.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=john.linn@xilinx.com \
--cc=josh.cartwright@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.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;
as well as URLs for NNTP newsgroup(s).