From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] PPC build fixes
Date: Mon, 21 Feb 2005 19:30:18 +0100 [thread overview]
Message-ID: <87bradpxz9.fsf@student.han.nl> (raw)
In-Reply-To: <346f53d6be98efc620fc845c6407a0cf@penguinppc.org> (Hollis Blanchard's message of "Sun, 20 Feb 2005 10:38:54 -0600")
Hollis Blanchard <hollis@penguinppc.org> writes:
> On Feb 20, 2005, at 7:39 AM, Yoshinori K. Okuji wrote:
>
>> On Sunday 20 February 2005 00:34, Hollis Blanchard wrote:
>>> - grub_reboot and grub_halt in util/i386/pc/misc.c are not
>>> architecture-specific, so have been moved to util/grub-emu.c.
>>
>> grub_halt is clearly arch-specific. Look at the definition grub_halt in
>> PC. It takes one argument, while the PPC version does not. I expect
>> that the same thing might happen in grub_reboot as well.
>
> Oops, I meant to convert that into using a more generic "flags"
> argument, and then "no_apm" becomes one bit in it. How would that be?
And how would the parser work? What if more options have to be added
for other archs? I do not have a strong objection against using
flags, I am just afraid it might be inadequate and that the current
code is easier to maintain.
Thanks,
Marco
next prev parent reply other threads:[~2005-02-21 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 23:34 [patch] PPC build fixes 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 [this message]
2005-02-21 18:28 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 3:00 Hollis Blanchard
2005-03-24 21:41 ` Marco Gerards
2005-03-25 14:58 ` Hollis Blanchard
2005-03-25 17:40 ` 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=87bradpxz9.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.