From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] PPC build fixes
Date: Fri, 25 Mar 2005 18:40:44 +0100 [thread overview]
Message-ID: <87zmwrsjxf.fsf@student.han.nl> (raw)
In-Reply-To: <760297805a8bd800c27a04d97b275c27@penguinppc.org> (Hollis Blanchard's message of "Fri, 25 Mar 2005 08:58:42 -0600")
Hollis Blanchard <hollis@penguinppc.org> writes:
[...]
> Because these commands need to be accessible from grub-emu (that is
> how you quit).
Oh, right.
>>> * include/grub/powerpc/ieee1275/init.h: Remove inaccurate
>>> comment.
>>
>> Can you change the comment to something sane?
>
> include/grub/i386/pc/init.h has no comment, and I don't know how to
> describe this anyways:
> void cmain (uint32_t r3, uint32_t r4, uint32_t r5);
> void grub_ofdisk_init (void);
> void grub_console_init (void);
> "A tiny bit of miscellaneous stuff"? "Things related to booting"?
Ok, just remove it. You are right again. :)
>>> * util/powerpc/ieee1275/misc.c (grub_reboot): New function.
>>> (grub_halt): Likewise.
>>
>> Isn't this just a completely new file?
>
> Er, yes, sorry. :)
Can you change these two lines to this:
* util/powerpc/ieee1275/misc.c: New file
If you do this, you could commit the patch. I can also do it if you
want. After this we can concentrate on getting that boot-path patch
committed. I will fix the initrd problem this weekend.
Thanks,
Marco
next prev parent reply other threads:[~2005-03-25 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 3:00 [patch] PPC build fixes Hollis Blanchard
2005-03-24 21:41 ` Marco Gerards
2005-03-25 14:58 ` Hollis Blanchard
2005-03-25 17:40 ` Marco Gerards [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-19 23:34 Hollis Blanchard
2005-02-20 13:39 ` Yoshinori K. Okuji
2005-02-20 16:38 ` Hollis Blanchard
2005-02-20 18:41 ` Yoshinori K. Okuji
2005-02-21 18:30 ` Marco Gerards
2005-02-21 18:28 ` Marco Gerards
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=87zmwrsjxf.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.