[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0g2AF7P=T-L_DJqLbOSAoqWcgZseTbeMCx9yChkNgFJOw@mail.gmail.com>
Date: Thu, 27 Aug 2015 01:16:41 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Toshi Kani <toshi.kani@...com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Rafael J Wysocki <rafael.j.wysocki@...el.com>,
Robert Moore <robert.moore@...el.com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Elliott, Robert (Server Storage)" <elliott@...com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
On Wed, Aug 26, 2015 at 11:12 PM, Toshi Kani <toshi.kani@...com> wrote:
> On Wed, 2015-08-26 at 10:16 -0700, Dan Williams wrote:
>> On Wed, Aug 26, 2015 at 9:20 AM, Toshi Kani <toshi.kani@...com> wrote:
>> > ACPI 6.0 NFIT Memory Device State Flags in Table 5-129 defines
>> > bit 3 as follows.
>> >
>> > Bit [3] set to 1 to indicate that the Memory Device is observed
>> > to be not armed prior to OSPM hand off. A Memory Device is
>> > considered armed if it is able to accept persistent writes.
>> >
>> > This bit is currently defined as ACPI_NFIT_MEM_ARMED, which can be
>> > confusing as if the Memory Device is armed when this bit is set.
>> >
>> > Change the name to ACPI_NFIT_MEM_NOT_ARMED per the spec.
>> >
>> > Signed-off-by: Toshi Kani <toshi.kani@...com>
>> > Cc: Dan Williams <dan.j.williams@...el.com>
>> > Cc: Bob Moore <robert.moore@...el.com>
>> > Cc: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>> > ---
>> > drivers/acpi/nfit.c | 6 +++---
>> > drivers/acpi/nfit.h | 2 +-
>> > include/acpi/actbl1.h | 2 +-
>>
>> This file "include/acpi/actbl1.h" is owned by the ACPICA project so
>> any changes need to come through them. But that said, I'm not sure we
>> need friendly names at this level.
>
> I think the name is misleading, but I agree with the process and this patch2
> can be dropped. It'd be nice if the ACPICA project can pick it up later
> when they have a chance, though.
A good way to cause that to happen would be to send a patch to the
ACPICA development list + maintainers as per MAINTAINERS.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists