From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] kern/err.c + disk/raid.c error handling fixes
Date: Thu, 14 Aug 2008 09:13:40 +0200 [thread overview]
Message-ID: <87vdy4yspn.fsf@xs4all.nl> (raw)
In-Reply-To: <1218670230.4010.11.camel@fz.local> (Felix Zielcke's message of "Thu, 14 Aug 2008 01:30:30 +0200")
Felix Zielcke <fzielcke@z-51.de> writes:
> Am Donnerstag, den 14.08.2008, 00:39 +0200 schrieb Felix Zielcke:
>>
>> This time dear Marco I didn't bother to read through the changelog, it
>> might be still not perfect and I'm even tired now.
>
> I should have better gone to bed instead of making quickly a patch for
> this.
> Well 2nd try now.
> I forgot grub-fstest and I think I know now why you said `why' to one
> entry ;)
> And I forgot to change the copyright year to 2008 for the new shiny
> util/err.c
So this patch isn't really required, but you want it for Lenny?
> 2008-08-14 Felix Zielcke <fzielcke@z-51.de>
>
> * include/grub/err.h (grub_error_stack_assert): New variable
> declaration.
> * kern/err.c (grub_error_stack_assert): Remove static.
> (grub_print_error): Disable it for [GRUB_UTIL] because ...
> * util/err.c: New file with grub_print_error () using fprintf
> (stderr, ...).
Can you just use misc.c?
> * conf/common.rmk: Add it for grub-probe.
I have been thinking of an alternative way to fix this. A bit of a
compromise between what you want and what I want and perhaps cleaner.
You could define a function grub_err_printf or something like that.
Which you use in grub_print_error. You can redefine it for
GRUB_UTIL to grub_util_error and to grub_print otherwise.
I didn't study the code. Will this be easier and cleaner?
--
Marco
next prev parent reply other threads:[~2008-08-14 7:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 16:28 [PATCH] kern/err.c + disk/raid.c error handling fixes Felix Zielcke
2008-08-12 16:32 ` Felix Zielcke
2008-08-12 21:42 ` Marco Gerards
2008-08-12 22:40 ` Robert Millan
2008-08-13 5:56 ` Felix Zielcke
2008-08-13 9:47 ` Marco Gerards
2008-08-13 20:31 ` Felix Zielcke
2008-08-13 20:38 ` Felix Zielcke
2008-08-13 21:50 ` Robert Millan
2008-08-13 22:39 ` Felix Zielcke
2008-08-13 23:30 ` Felix Zielcke
2008-08-14 7:13 ` Marco Gerards [this message]
2008-08-14 11:02 ` Felix Zielcke
2008-08-14 18:08 ` Robert Millan
2008-08-14 18:16 ` Vesa Jääskeläinen
2008-08-14 18:27 ` Marco Gerards
2008-08-14 18:48 ` Felix Zielcke
2008-08-13 23:32 ` Robert Millan
2008-08-13 9: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=87vdy4yspn.fsf@xs4all.nl \
--to=mgerards@xs4all.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.