From: Roman Zippel <zippel@linux-m68k.org>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: paulus@samba.org, linuxppc-commit@ppcbk.mvista.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: rearrangements in linuxppc_2_4_devel
Date: Thu, 28 Jun 2001 00:00:11 +0200 [thread overview]
Message-ID: <3B3A576B.6D2968A8@linux-m68k.org> (raw)
In-Reply-To: 3B39E532.7040202@humboldt.co.uk
Hi,
Adrian Cox wrote:
> Looking at the makefile, APUS links with setup.c. So it's going to link
> with our standard parse_bootinfo, which doesn't take any arguments. I
> suspect APUS needs a bit more work to integrate it into the 2_4_devel tree.
Yes, APUS currently calls its own parse_bootinfo() (amiga/bootinfo.c) in
apus_init().
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-06-27 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 6:46 rearrangements in linuxppc_2_4_devel Paul Mackerras
2001-06-27 11:51 ` Adrian Cox
2001-06-27 12:43 ` Paul Mackerras
2001-06-27 13:52 ` Adrian Cox
2001-06-27 22:00 ` Roman Zippel [this message]
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=3B3A576B.6D2968A8@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-commit@ppcbk.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).