From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] orion5x and footbridge compile fixes for 3.1
Date: Fri, 26 Aug 2011 11:05:44 -0500 [thread overview]
Message-ID: <4E57C458.9020805@gmail.com> (raw)
In-Reply-To: <201108261753.03086.arnd@arndb.de>
Arnd,
On 08/26/2011 10:53 AM, Arnd Bergmann wrote:
> On Thursday 25 August 2011, Rob Herring wrote:
>> Please pull for 3.1-rc. Footbridge and orion5x builds are currently
>> broken in 3.1 mainly due to my changes in this commit:
>>
>> commit cc22b4c18540e5e8bf55c7d124044f9317527d3c
>> Author: Rob Herring <rob.herring@calxeda.com>
>> Date: Tue Jun 28 21:22:40 2011 -0500
>>
>> ARM: set vga memory base at run-time
>>
>>
>> The following changes since commit fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c:
>>
>
> Pulled, thanks!
>
> BTW, are you planning to get your own git tree in the future or do you keep using
> Jon's git.jdl.com server?
It is mine basically, just on Jon's domain. But yes, it's on the IT guys
todo list... Jon was just the quickest path.
>
> It should be no problem for you to get hosting on git.kernel.org, there is
> a FAQ somewhere. With the current situation, it's now clear from the changelog
> why I am pulling patches from Jon's server with your Signed-off-by.
>
Why would 3 Marvell patches from me be strange... :)
It wasn't really clear to me whether you were going to pick them off the
list and were aware of all 3 patches, so I just decided to make it easy
for you.
Rob
next prev parent reply other threads:[~2011-08-26 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 14:23 [GIT PULL] orion5x and footbridge compile fixes for 3.1 Rob Herring
2011-08-25 15:37 ` Paul Gortmaker
2011-08-26 15:53 ` Arnd Bergmann
2011-08-26 16:05 ` Rob Herring [this message]
2011-08-26 16:18 ` 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=4E57C458.9020805@gmail.com \
--to=robherring2@gmail.com \
--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).