From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: SBS Palomar II/IV/V port
Date: Thu, 11 Oct 01 18:53:12 PDT [thread overview]
Message-ID: <0110120153.AA28702@ivan.Harhan.ORG> (raw)
Tom Rini <trini@kernel.crashing.org> wrote:
> Okay, does the following look right/work for everyone?
>
> [...]
>
> - initrd_end = data[0] + rec->size;
> + initrd_end = data[0] + data[1];
This should work for me.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-12 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 1:53 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 20:13 SBS Palomar II/IV/V port Michael Sokolov
[not found] <0110092125.AA22665@ivan.Harhan.ORG>
2001-10-10 18:24 ` 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
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=0110120153.AA28702@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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).