From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH]: grub: Fix handling of long printf arguments on 64-bit.
Date: Sun, 12 Apr 2009 17:36:18 -0400 [thread overview]
Message-ID: <1239572178.14481.35.camel@ct> (raw)
In-Reply-To: <200904121019.18535.ml@isaac.cedarswampstudios.org>
On Sun, 2009-04-12 at 10:19 -0400, Isaac Dupree wrote:
> > - grub_ltoa (tmp, c, l);
> > + grub_lltoa (tmp, c, l);
> > }
> > else
> > {
> > n = va_arg (args, int);
> > - grub_itoa (tmp, c, n);
> > + grub_lltoa (tmp, c, n);
>
> Do you think they deserve a comment saying why lltoa and that e.g. grub_ltoa
> would work equally well there except for space reasons? (In case we ever
> decided to change that code back, it would be easier to figure out.)
If somebody wants to change the code back, that person would need to
justify adding two functions to kern/misc.c, which is part of the GRUB
core and should be kept minimal. I don't think it will be easy to
justify.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-04-12 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 8:08 [PATCH]: grub: Fix handling of long printf arguments on 64-bit David Miller
2009-04-11 10:19 ` Yoshinori K. Okuji
2009-04-11 11:48 ` David Miller
2009-04-11 19:10 ` phcoder
2009-04-12 3:21 ` Pavel Roskin
2009-04-12 8:07 ` David Miller
2009-04-12 12:46 ` phcoder
2009-04-12 14:19 ` Isaac Dupree
2009-04-12 21:36 ` Pavel Roskin [this message]
2009-04-12 21:33 ` Pavel Roskin
2009-04-12 21:51 ` Pavel Roskin
2009-04-12 22:19 ` phcoder
2009-04-13 5:23 ` Pavel Roskin
2009-04-15 12:46 ` phcoder
2009-04-12 6:39 ` Pavel Roskin
2009-04-12 8:05 ` David Miller
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=1239572178.14481.35.camel@ct \
--to=proski@gnu.org \
--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.