linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: [PATCH] ppc32: Add missing initrd header on ppc440
Date: Mon, 31 Oct 2005 11:29:13 +0200	[thread overview]
Message-ID: <200510311029.13432.sr@denx.de> (raw)
In-Reply-To: <200510281758.56646.sr@denx.de>

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

Sorry, but this missing header slipped though last time. Please apply.

Signed-off-by: Stefan Roese <sr@denx.de>

By the way: What is the current status of the pending 4xx patches. Are they 
going in in this 2-week merge window?

Best regards,
Stefan

[-- Attachment #2: ppc440-initrd-header-added.patch --]
[-- Type: text/x-diff, Size: 900 bytes --]

[PATCH] ppc32: Add missing initrd header on ppc440

Signed-off-by: Stefan Roese <sr@denx.de>

---
commit 54069303584813d4f0bafcd04bb2b7b0e9fc4693
tree 319e03ffc9097b7a8376b6e3108b4249f6d6dc0d
parent d8832f2614a9bfdb445a62a23e80f01886ae661e
author Stefan Roese <sr@denx.de> Mon, 31 Oct 2005 10:20:52 +0100
committer Stefan Roese <sr@denx.de> Mon, 31 Oct 2005 10:20:52 +0100

 arch/ppc/syslib/ibm44x_common.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/ppc/syslib/ibm44x_common.c b/arch/ppc/syslib/ibm44x_common.c
index 5152c8e..6dae518 100644
--- a/arch/ppc/syslib/ibm44x_common.c
+++ b/arch/ppc/syslib/ibm44x_common.c
@@ -20,6 +20,7 @@
 #include <linux/types.h>
 #include <linux/serial.h>
 #include <linux/module.h>
+#include <linux/initrd.h>
 
 #include <asm/ibm44x.h>
 #include <asm/mmu.h>


\f
!-------------------------------------------------------------flip-



  reply	other threads:[~2005-10-31  9:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  1:31 Address mapping PPC 405 P. Sadik
2005-08-26  3:10 ` Grant Likely
2005-08-26 22:47   ` Peter Ryser
2005-08-28 15:15 ` Jon Masters
2005-08-29  0:26   ` Grant Likely
2005-08-29  1:11     ` Jon Masters
2005-08-30 15:38       ` Matt Porter
2005-09-15 16:03         ` PPC4xx cleanup Stefan Roese
2005-09-15 16:25           ` Matt Porter
2005-09-15 19:03             ` Dan Malek
2005-09-19 14:08               ` Matt Porter
2005-09-16 11:06             ` [PATCH] ppc32: cleanup AMCC PPC4xx eval boards to better support U-Boot Stefan Roese
2005-09-16 16:27               ` Eugene Surovegin
2005-09-19 11:02                 ` Stefan Roese
2005-09-19 13:59                   ` Matt Porter
2005-09-19 15:06                     ` Stefan Roese
2005-09-19 15:21                       ` Matt Porter
2005-09-19 17:14                       ` Eugene Surovegin
2005-11-22 17:34               ` [PATCH] ppc32: Add P3P440 (440GP) board support Stefan Roese
2005-09-19 11:20             ` [PATCH] ppc32: cleanup AMCC PPC44x eval boards to better support U-Boot Stefan Roese
2005-09-30 12:52               ` [PATCH] ppc32: cleanup AMCC PPC40x eval boards to " Stefan Roese
2005-10-28 15:58                 ` [PATCH] ppc32: Remove internal PCI arbiter check on PPC40x Stefan Roese
2005-10-31  9:29                   ` Stefan Roese [this message]
2005-10-31 14:41                     ` [PATCH] ppc32: Add missing initrd header on ppc440 Matt Porter
2005-08-30 15:09     ` Address mapping PPC 405 Matt Porter

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=200510311029.13432.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-embedded@ozlabs.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).