From: Bean <bean123ch@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Handler support
Date: Mon, 2 Mar 2009 01:52:21 +0800 [thread overview]
Message-ID: <ca0f59980903010952o372c2d07v287dcbea7416cbc4@mail.gmail.com> (raw)
In-Reply-To: <ca0f59980902272141h2c4c8320o961c967eb2c688ef@mail.gmail.com>
On Sat, Feb 28, 2009 at 1:41 PM, Bean <bean123ch@gmail.com> wrote:
> On Sat, Feb 28, 2009 at 3:54 AM, Robert Millan <rmh@aybabtu.com> wrote:
>> On Sun, Feb 15, 2009 at 11:14:18PM +0800, Bean wrote:
>>> diff --git a/conf/sparc64-ieee1275.rmk b/conf/sparc64-ieee1275.rmk
>>> index 640ceda..18c108e 100644
>>> --- a/conf/sparc64-ieee1275.rmk
>>> +++ b/conf/sparc64-ieee1275.rmk
>>
>> Don't bother updating sparc64-ieee1275.rmk, it's completely broken by now.
>>
>>> void
>>> grub_term_register_input (grub_term_input_t term)
>>> {
>>> - term->next = grub_term_list_input;
>>> - grub_term_list_input = term;
>>> - if (! grub_cur_term_input)
>>> - grub_term_set_current_input (term);
>>> + grub_handler_register (&grub_term_input_class, GRUB_AS_HANDLER (term));
>>> }
>>
>> Is grub_handler_register() always used this way? Perhaps it should be
>> inline.
>
> Hi,
>
> Good point. In fact, I change all occurrence of
> grub_term_register_input to grub_handler_register previously, but
> considered the amount of code to change, I decide to provide the
> wrapper function grub_term_register_input. Using inline function would
> utilize the new handler infrastructure while retaining code
> compatibility.
Hi,
Fixed and committed.
--
Bean
next prev parent reply other threads:[~2009-03-01 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 12:01 [PATCH] Handler support Bean
2009-02-14 14:46 ` Bean
2009-02-14 15:11 ` Felix Zielcke
2009-02-14 15:28 ` Bean
2009-02-15 7:32 ` Vesa Jääskeläinen
2009-02-15 8:58 ` Bean
2009-02-15 15:14 ` Bean
2009-02-22 19:40 ` Bean
2009-02-27 19:54 ` Robert Millan
2009-02-28 5:41 ` Bean
2009-03-01 17:52 ` Bean [this message]
2009-03-04 20:55 ` Robert Millan
2009-03-05 5:34 ` Bean
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=ca0f59980903010952o372c2d07v287dcbea7416cbc4@mail.gmail.com \
--to=bean123ch@gmail.com \
--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.