From: Peter Bergner <bergner@brule.borg.umn.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Val Henson <val@nmt.edu>,
Michael Sokolov <msokolov@ivan.Harhan.ORG>,
linuxppc-dev@lists.linuxppc.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: SBS Palomar II/IV/V port
Date: Fri, 12 Oct 2001 11:26:19 -0500 [thread overview]
Message-ID: <20011012112619.A281146@brule.borg.umn.edu> (raw)
In-Reply-To: <20011011161848.B21564@cpe-24-221-152-185.az.sprintbbd.net>
: Okay, does the following look right/work for everyone? (With a similar
: change to arch/ppc64/kernel/setup.c).
:
: ===== arch/ppc/kernel/setup.c 1.60 vs edited =====
: --- 1.60/arch/ppc/kernel/setup.c Thu Sep 27 09:01:14 2001
: +++ edited/arch/ppc/kernel/setup.c Thu Oct 11 16:15:45 2001
: @@ -496,7 +496,7 @@
: #ifdef CONFIG_BLK_DEV_INITRD
: case BI_INITRD:
: initrd_start = data[0];
: - initrd_end = data[0] + rec->size;
: + initrd_end = data[0] + data[1];
: break;
: #endif /* CONFIG_BLK_DEV_INITRD */
: #ifdef CONFIG_ALL_PPC
That's one of the changes I already have for PPC64, so looks good to me too.
Peter
--
Peter Bergner
SLIC Optimizing Translator Development / Linux PPC64 Kernel Development
IBM Rochester, MN
bergner@vnet.ibm.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-12 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0110092125.AA22665@ivan.Harhan.ORG>
2001-10-10 18:24 ` SBS Palomar II/IV/V port Val Henson
2001-10-10 21:30 ` Benjamin Herrenschmidt
2001-10-11 1:05 ` Tom Rini
2001-10-10 23:57 ` Paul Mackerras
2001-10-11 1:06 ` Tom Rini
2001-10-11 13:11 ` Peter Bergner
2001-10-11 23:18 ` Tom Rini
2001-10-12 16:26 ` Peter Bergner [this message]
2001-10-10 20:13 Michael Sokolov
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 1:53 Michael Sokolov
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=20011012112619.A281146@brule.borg.umn.edu \
--to=bergner@brule.borg.umn.edu \
--cc=bergner@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.ORG \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.org \
--cc=val@nmt.edu \
/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).