From: Linda Knippers <linda.knippers@hp.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
Rafael J Wysocki <rafael.j.wysocki@intel.com>,
Robert Moore <robert.moore@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Elliott, Robert (Server Storage)" <elliott@hp.com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
Date: Thu, 27 Aug 2015 12:32:39 -0400 [thread overview]
Message-ID: <55DF3BA7.7070909@hp.com> (raw)
In-Reply-To: <CAPcyv4h8iu+4yWvREyocdfFKDEo6QsV_17z=kougVBZNCeRjaQ@mail.gmail.com>
On 8/27/2015 11:54 AM, Dan Williams wrote:
> On Thu, Aug 27, 2015 at 8:35 AM, Linda Knippers <linda.knippers@hp.com> wrote:
>> On 8/27/2015 11:30 AM, Dan Williams wrote:
>>> On Thu, Aug 27, 2015 at 7:43 AM, Linda Knippers <linda.knippers@hp.com> wrote:
>>>> I don't see why we can't fix the names so they make sense now before there
>>>> is hardware in the market. People doing testing and debugging look at stuff
>>>> in /sys and they write their own scripts too, not necessarily in python.
>>>
>>> The practical concern at this point is that it is too late in the 4.2
>>> development cycle, in my opinion, to push for a cosmetic change like
>>> this. We also have versions of libndctl starting to leak into
>>> distributions. Changing this in 4.3 means breaking the ABI from 4.2
>>> and managing both ways in future versions of the library as well as
>>> getting all distributions to update. Not insurmountable, but also
>>> something I don't want to take on just for a few characters in a sysfs
>>> file. I think this is better fixed with documentation which I still
>>> owe to the the Documentation/ABI/ directory.
>>
>> Is there any distribution that is going to enable this with 4.2? I know
>> we're using it for testing now but there is still quite a bit of work
>> queued up for 4.3 and more still left to be done.
>
> I'm not happy that this is confusing folks, and it is unfortunate that
> the polarity is reversed.
>
> However, I'm more concerned about the fact that I'd be knowingly
> breaking ABI from 4.2 to 4.3. I originally thought "no one" was using
> e820 type-12 for enumerating nvdimm resources, but I got shouted down
> when trying to convert that exclusively to the ACPI 6 definition. The
> Linus edict of "we don't break released ABI" is ringing in my ears.
Maybe not too late for 4.2 then. They're just string changes.
> The current name is also consistent with the current / released ACPICA
> definition.
They seem to be open to fixing it.
I know this seems like a nit but we've going to live with this stuff for
a long time.
-- ljk
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Linda Knippers <linda.knippers@hp.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
Rafael J Wysocki <rafael.j.wysocki@intel.com>,
Robert Moore <robert.moore@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Elliott, Robert (Server Storage)" <elliott@hp.com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
Date: Thu, 27 Aug 2015 12:32:39 -0400 [thread overview]
Message-ID: <55DF3BA7.7070909@hp.com> (raw)
In-Reply-To: <CAPcyv4h8iu+4yWvREyocdfFKDEo6QsV_17z=kougVBZNCeRjaQ@mail.gmail.com>
On 8/27/2015 11:54 AM, Dan Williams wrote:
> On Thu, Aug 27, 2015 at 8:35 AM, Linda Knippers <linda.knippers@hp.com> wrote:
>> On 8/27/2015 11:30 AM, Dan Williams wrote:
>>> On Thu, Aug 27, 2015 at 7:43 AM, Linda Knippers <linda.knippers@hp.com> wrote:
>>>> I don't see why we can't fix the names so they make sense now before there
>>>> is hardware in the market. People doing testing and debugging look at stuff
>>>> in /sys and they write their own scripts too, not necessarily in python.
>>>
>>> The practical concern at this point is that it is too late in the 4.2
>>> development cycle, in my opinion, to push for a cosmetic change like
>>> this. We also have versions of libndctl starting to leak into
>>> distributions. Changing this in 4.3 means breaking the ABI from 4.2
>>> and managing both ways in future versions of the library as well as
>>> getting all distributions to update. Not insurmountable, but also
>>> something I don't want to take on just for a few characters in a sysfs
>>> file. I think this is better fixed with documentation which I still
>>> owe to the the Documentation/ABI/ directory.
>>
>> Is there any distribution that is going to enable this with 4.2? I know
>> we're using it for testing now but there is still quite a bit of work
>> queued up for 4.3 and more still left to be done.
>
> I'm not happy that this is confusing folks, and it is unfortunate that
> the polarity is reversed.
>
> However, I'm more concerned about the fact that I'd be knowingly
> breaking ABI from 4.2 to 4.3. I originally thought "no one" was using
> e820 type-12 for enumerating nvdimm resources, but I got shouted down
> when trying to convert that exclusively to the ACPI 6 definition. The
> Linus edict of "we don't break released ABI" is ringing in my ears.
Maybe not too late for 4.2 then. They're just string changes.
> The current name is also consistent with the current / released ACPICA
> definition.
They seem to be open to fixing it.
I know this seems like a nit but we've going to live with this stuff for
a long time.
-- ljk
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-08-27 16:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:20 [PATCH 0/2]: acpi, nfit: Clarify memory device state flags Toshi Kani
2015-08-26 16:20 ` Toshi Kani
2015-08-26 16:20 ` [PATCH 1/2]: nfit: Clarify memory device state flags strings Toshi Kani
2015-08-26 16:20 ` Toshi Kani
2015-08-27 3:07 ` Ross Zwisler
2015-08-27 3:07 ` Ross Zwisler
2015-08-27 14:18 ` Toshi Kani
2015-08-27 14:18 ` Toshi Kani
2015-08-27 18:57 ` Dan Williams
2015-08-27 18:57 ` Dan Williams
2015-08-27 19:02 ` Toshi Kani
2015-08-27 19:02 ` Toshi Kani
2015-08-26 16:20 ` [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition Toshi Kani
2015-08-26 16:20 ` Toshi Kani
2015-08-26 17:16 ` Dan Williams
2015-08-26 17:16 ` Dan Williams
2015-08-26 19:59 ` Linda Knippers
2015-08-26 19:59 ` Linda Knippers
2015-08-26 21:12 ` Toshi Kani
2015-08-26 21:12 ` Toshi Kani
2015-08-26 21:30 ` Dan Williams
2015-08-26 21:30 ` Dan Williams
2015-08-26 21:44 ` Toshi Kani
2015-08-26 21:44 ` Toshi Kani
2015-08-26 22:00 ` Dan Williams
2015-08-26 22:00 ` Dan Williams
2015-08-27 14:43 ` Linda Knippers
2015-08-27 14:43 ` Linda Knippers
2015-08-27 15:30 ` Dan Williams
2015-08-27 15:30 ` Dan Williams
2015-08-27 15:35 ` Linda Knippers
2015-08-27 15:35 ` Linda Knippers
2015-08-27 15:54 ` Dan Williams
2015-08-27 15:54 ` Dan Williams
2015-08-27 16:32 ` Linda Knippers [this message]
2015-08-27 16:32 ` Linda Knippers
2015-08-27 17:04 ` Dan Williams
2015-08-27 17:04 ` Dan Williams
2015-08-27 17:09 ` Linda Knippers
2015-08-27 17:09 ` Linda Knippers
2015-08-26 23:16 ` Rafael J. Wysocki
2015-08-26 23:16 ` Rafael J. Wysocki
2015-08-26 23:29 ` Toshi Kani
2015-08-26 23:29 ` Toshi Kani
2015-08-26 23:35 ` Toshi Kani
2015-08-26 23:35 ` Toshi Kani
2015-08-27 1:56 ` Moore, Robert
2015-08-27 1:56 ` Moore, Robert
2015-08-27 14:32 ` Toshi Kani
2015-08-27 14:32 ` Toshi Kani
2015-08-27 14:32 ` 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=55DF3BA7.7070909@hp.com \
--to=linda.knippers@hp.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=toshi.kani@hp.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 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.