From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] orion5x and footbridge compile fixes for 3.1
Date: Thu, 25 Aug 2011 11:37:11 -0400 [thread overview]
Message-ID: <4E566C27.3020409@windriver.com> (raw)
In-Reply-To: <4E565AC4.7060504@gmail.com>
On 11-08-25 10:23 AM, Rob Herring wrote:
> Arnd,
>
> 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:
>
> Linux 3.1-rc3 (2011-08-22 11:42:53 -0700)
>
> are available in the git repository at:
> git://git.jdl.com/software/linux-3.0.git fixes
>
> Bryan Wu (2):
> ARM: mach-orion5x: add missing header file <linux/vga.h>
> ARM: mach-footbridge: add missing header file <video/vga.h>
I had similar commits to the two above in the module.h tree
(in linux-next) since I thought the missing vga.h was fallout
from the implicit presence of module.h everywhere.
I'll drop all three from linux-next now that they are scheduled
for pulling into 3.1-rcN.
Thanks,
Paul.
>
> Paul Gortmaker (1):
> arm: fix compile failure in orion5x/dns323-setup.c
>
> arch/arm/mach-footbridge/dc21285.c | 1 +
> arch/arm/mach-orion5x/dns323-setup.c | 2 +-
> arch/arm/mach-orion5x/pci.c | 1 +
> 3 files changed, 3 insertions(+), 1 deletions(-)
>
> Rob
next prev parent reply other threads:[~2011-08-25 15:37 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 [this message]
2011-08-26 15:53 ` Arnd Bergmann
2011-08-26 16:05 ` Rob Herring
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=4E566C27.3020409@windriver.com \
--to=paul.gortmaker@windriver.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).