All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] Incorrect NFIT GUID strings in ACPICA 20150515
Date: Fri, 22 May 2015 10:58:13 -0600	[thread overview]
Message-ID: <555F6025.8030803@redhat.com> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E37D2EEE27@ORSMSX112.amr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

On 05/22/2015 10:34 AM, Moore, Robert wrote:
> The GUID strings for the ACPI 6.0 NFIT table were incorrect in the recent version of ACPICA (20150515). Here are the corrected strings:
> 
> 
> (From include/acuuid.h):
> 
> /* NVDIMM - NFIT table */
> 
> #define UUID_VOLATILE_MEMORY            "7305944f-fdda-44e3-b16c-3f22d252e5d0"
> #define UUID_PERSISTENT_MEMORY          "66f0d379-b4f3-4074-ac43-0d3318b78cdb"
> #define UUID_CONTROL_REGION             "92f701f6-13b4-405d-910b-299367e8234c"
> #define UUID_DATA_REGION                "91af0530-5d86-470e-a6b0-0a2db9408249"
> #define UUID_VOLATILE_VIRTUAL_DISK      "77ab535a-45fc-624b-5560-f7b281d1f96e"
> #define UUID_VOLATILE_VIRTUAL_CD        "3d5abd30-4175-87ce-6d64-d2ade523c4bb"
> #define UUID_PERSISTENT_VIRTUAL_DISK    "5cea02c9-4d07-69d3-269f-4496fbe096f9"
> #define UUID_PERSISTENT_VIRTUAL_CD      "08018188-42cd-bb48-100f-5387d53ded3d"
> 
> Sorry for any inconvenience.
> Bob
> 

Will there be a 20150522 (or so) release then?  Or will we just wait until
the next cycle?  Either way, I'll make sure these values get into the distro
packages (i.e., patch 20150515 or use the new version).

Thanks.

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------

             reply	other threads:[~2015-05-22 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 16:58 Al Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-22 17:16 [Devel] Incorrect NFIT GUID strings in ACPICA 20150515 Moore, Robert
2015-05-22 16:34 Moore, Robert

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=555F6025.8030803@redhat.com \
    --to=devel@acpica.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.