linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hpe.com>
To: rjw@rjwysocki.net, dan.j.williams@intel.com
Cc: robert.moore@intel.com, elliott@hpe.com,
	linux-nvdimm@lists.01.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@acpica.org
Subject: [PATCH 0/2] ACPI 6.1 update for NFIT Control Region Structure
Date: Fri, 19 Feb 2016 16:08:51 -0700	[thread overview]
Message-ID: <1455923333-13629-1-git-send-email-toshi.kani@hpe.com> (raw)

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure
as follows.
 - Valid Fields, Manufacturing Location, and Manufacturing Date
   are added from reserved range.  No change in the structure size.
 - IDs defined as SPD values are arrays of bytes.  The spec 
   clarified that they need to be represented as arrays of bytes
   as well.

Patch 1 changes 'struct acpi_nfit_control_region' and the NFIT driver.
Patch 2 changes the nfit test driver.

link: http://www.uefi.org/sites/default/files/resources/ACPI_6_1.pdf

---
Toshi Kani (2):
 1/2 ACPI/NFIT: Update Control Region Structure per ACPI 6.1
 2/2 nfit_test: Update SPD ID init handlings

---
 drivers/acpi/nfit.c              | 75 ++++++++++++++++++++++++++++++++++------
 include/acpi/actbl1.h            | 24 ++++++++-----
 tools/testing/nvdimm/test/nfit.c | 64 ++++++++++++++++++++--------------
 3 files changed, 119 insertions(+), 44 deletions(-)

             reply	other threads:[~2016-02-19 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 23:08 Toshi Kani [this message]
2016-02-19 23:08 ` [PATCH 1/2] ACPI/NFIT: Update Control Region Structure per ACPI 6.1 Toshi Kani
2016-02-19 22:34   ` Dan Williams
2016-02-19 22:55     ` Moore, Robert
2016-02-19 23:44     ` Toshi Kani
2016-02-19 23:08 ` [PATCH 2/2] nfit_test: Update SPD ID init handlings Toshi Kani

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=1455923333-13629-1-git-send-email-toshi.kani@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=devel@acpica.org \
    --cc=elliott@hpe.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@intel.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;
as well as URLs for NNTP newsgroup(s).