[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1456861992.15454.90.camel@hpe.com>
Date: Tue, 01 Mar 2016 12:53:12 -0700
From: Toshi Kani <toshi.kani@....com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: "Moore, Robert" <robert.moore@...el.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"Zheng, Lv" <lv.zheng@...el.com>,
"elliott@....com" <elliott@....com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...ica.org" <devel@...ica.org>
Subject: Re: [PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to
comply ACPI 6.1
On Tue, 2016-03-01 at 10:14 -0800, Dan Williams wrote:
> On Tue, Mar 1, 2016 at 9:36 AM, Toshi Kani <toshi.kani@....com> wrote:
> > On Tue, 2016-03-01 at 16:03 +0000, Moore, Robert wrote:
:
> I think the "ACPI tables are little-endian" assumption is pervasive
> throughout the implementation.
>
> Toshi, it seems all we need is conversions like:
>
> - sprintf(buf, "%#x\n", dcr->vendor_id);
> + sprintf(buf, "%#x\n", le16_to_cpu(dcr->vendor_id));
nit - I think it needs to be be16_to_cpu() if I understand this macro
correctly.
-Toshi
>
> ...for the values exported to userspace through sysfs, but otherwise
> leave the base table definitions as is. Will this suffice?
Powered by blists - more mailing lists