From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] vexpress: soc changes for v3.8
Date: Fri, 26 Oct 2012 17:00:51 +0000 [thread overview]
Message-ID: <201210261700.52195.arnd@arndb.de> (raw)
In-Reply-To: <1351270481.9454.34.camel@hornet>
On Friday 26 October 2012, Pawel Moll wrote:
> On Fri, 2012-10-26 at 17:44 +0100, Arnd Bergmann wrote:
> > On Thursday 18 October 2012, Pawel Moll wrote:
> > > ARM: vexpress: Start using new Versatile Express infrastructure
> >
> > This patch introduces calls to vexpress_clk_of_init and other functions
> > that don't yet exist. Can you send a fixup?
>
> The clocking stuff should already be in the -next - Mike pulled it over
> two weeks ago. In any case the branch is here:
Right, it works in -next. Can you rebase the soc changes on top of the
stuff that went into Mike's tree and resubmit so it also builds in
arm-soc?
Arnd
next prev parent reply other threads:[~2012-10-26 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 17:05 [GIT PULL] vexpress: soc changes for v3.8 Pawel Moll
2012-10-26 13:37 ` Arnd Bergmann
2012-10-26 14:02 ` Pawel Moll
2012-10-26 16:44 ` Arnd Bergmann
2012-10-26 16:54 ` Pawel Moll
2012-10-26 17:00 ` Arnd Bergmann [this message]
2012-10-26 17:10 ` Pawel Moll
2012-10-26 17:18 ` Arnd Bergmann
2012-10-26 17:45 ` Pawel Moll
2012-10-26 19:26 ` Arnd Bergmann
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=201210261700.52195.arnd@arndb.de \
--to=arnd@arndb.de \
--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).