From: Matthew Garrett <mjg@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmi, Use little-endian for sysfs PRODUCT UUID
Date: Tue, 27 Mar 2012 17:09:07 +0100 [thread overview]
Message-ID: <20120327160907.GB8398@srcf.ucam.org> (raw)
In-Reply-To: <1332785571-1475-1-git-send-email-prarit@redhat.com>
On Mon, Mar 26, 2012 at 02:12:51PM -0400, Prarit Bhargava wrote:
> Although RFC 4122 recommends network byte order for all fields, the PC
> industry (including the ACPI, UEFI, and Microsoft specifications) has
> consistently used little-endian byte encoding for the first three
> fields: time_low, time_mid, time_hi_and_version. The same encoding, also
> known as wire format, should also be used for the SMBIOS representation of
> the UUID.
There's some potential for breakage here. Perhaps add an additional
attribute that adds the purely little-endian UUID?
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2012-03-27 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:12 [PATCH] dmi, Use little-endian for sysfs PRODUCT UUID Prarit Bhargava
2012-03-27 16:09 ` Matthew Garrett [this message]
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=20120327160907.GB8398@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
/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