From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix CPUID documentation and return values
Date: Fri, 31 Jul 2009 18:07:48 +0200 [thread overview]
Message-ID: <20090731160748.GG14675@thorin> (raw)
In-Reply-To: <d7ead6de0907281405p879f50bv697420c8275b8fbd@mail.gmail.com>
On Tue, Jul 28, 2009 at 11:05:37PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Tue, Jul 28, 2009 at 8:15 PM, Robert Millan<rmh@aybabtu.com> wrote:
> > On Tue, Jul 28, 2009 at 01:03:51AM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >> Hello. CPUID command currently doesn't return a real grub_err_t and
> >> errors aren't set which doesn't fit in grub2's design.
> >> Addirionally "help cpuid" doesn't give really useful info. So for
> >> future expandability and less confusion I propose the attached patch
> >> partially based on original patch by Robert Millan
> >
> > Hi,
> >
> > I don't remember about this patch. I assume I wrote it in 2007 when
> > merging cpuid support for first time.
> Yes, it is.
> > Any idea why it wasn't it committed
> > back then?
> >
> None. Yoshinori K Okuji approved it here:
> http://lists.gnu.org/archive/html/grub-devel/2007-05/msg00148.html
I vaguely recall having disabled it because there was some issue with
scripting. Assuming it's working properly now, I have no objection with
it.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-31 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 23:03 [PATCH] Fix CPUID documentation and return values Vladimir 'phcoder' Serbinenko
2009-07-28 18:15 ` Robert Millan
2009-07-28 21:05 ` Vladimir 'phcoder' Serbinenko
2009-07-31 16:07 ` Robert Millan [this message]
2009-07-31 16:19 ` Felix Zielcke
2009-07-31 16:26 ` Robert Millan
2009-07-31 16:41 ` Felix Zielcke
2009-08-01 14:23 ` Robert Millan
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=20090731160748.GG14675@thorin \
--to=rmh@aybabtu.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.