From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: new GPT and uuid patches
Date: Tue, 11 Dec 2001 05:44:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805681@msgid-missing> (raw)
>>>>> On Mon, 10 Dec 2001 22:17:06 -0600, Matt_Domsch@Dell.com said:
Matt> to be useful in more places. I withdraw my previous patch
Matt> implementing uuid.[ch] as libraries, letting efi_guid_t remain
Matt> it's own unique thing. It was hard enough getting the crc32
Matt> library patch submitted, making other non-critical library
Matt> cleanups is more than I can handle ATM.
Most of the patch looks good to me, but I do not understand why you
want to use a structured type for GUID. This really does make the
whole store much more complicated than it has to be. As per our
earlier discussion with Linus and Alan, the GUID should be just an
unstructured sequence of 16 bytes. If you do that, all those ugly
conversion routines can go away and your head doesn't spin trying to
figure out what needs to be big-endian and what needs to be little
endian. The *only* thing that needs to be endian aware is the
parsing/printing routines. Those will be EFI GUID specific and will
have to make up for the mistake Intel made when defining the external
representation in the weird mixed byteorder (well, I'm assuming it was
a mistake; I don't assume someone would willfully do such a thing ;-).
The other benefit is that this will make GUIDs identical to UUIDs
(which they ought be), except for the external representation.
--david
next reply other threads:[~2001-12-11 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 5:44 David Mosberger [this message]
2001-12-11 15:40 ` [Linux-ia64] RE: new GPT and uuid patches Matt_Domsch
2001-12-11 21:40 ` Matt Domsch
2001-12-12 3:55 ` Matt Domsch
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=marc-linux-ia64-105590698805681@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox