From: Toshi Kani <toshi.kani@hp.com>
To: "Moore, Robert" <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@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>,
"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
Date: Thu, 27 Aug 2015 08:32:03 -0600 [thread overview]
Message-ID: <1440685923.14237.89.camel@hp.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D340BD7@ORSMSX112.amr.corp.intel.com>
On Thu, 2015-08-27 at 01:56 +0000, Moore, Robert wrote:
> I don’t have any problem changing this in ACPICA if/when you all agree.
Great. I will resend this patch alone, assuming the patch can be based on
the Dan's NVDIMM tree (since it changes NFIT files).
Thanks,
-Toshi
--
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: Toshi Kani <toshi.kani@hp.com>
To: "Moore, Robert" <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@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>,
"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
Date: Thu, 27 Aug 2015 08:32:03 -0600 [thread overview]
Message-ID: <1440685923.14237.89.camel@hp.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D340BD7@ORSMSX112.amr.corp.intel.com>
On Thu, 2015-08-27 at 01:56 +0000, Moore, Robert wrote:
> I don’t have any problem changing this in ACPICA if/when you all agree.
Great. I will resend this patch alone, assuming the patch can be based on
the Dan's NVDIMM tree (since it changes NFIT files).
Thanks,
-Toshi
WARNING: multiple messages have this Message-ID (diff)
From: Toshi Kani <toshi.kani@hp.com>
To: "Moore, Robert" <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@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>,
"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH 2/2]: acpica/nfit: Rename not-armed bit definition
Date: Thu, 27 Aug 2015 08:32:03 -0600 [thread overview]
Message-ID: <1440685923.14237.89.camel@hp.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D340BD7@ORSMSX112.amr.corp.intel.com>
On Thu, 2015-08-27 at 01:56 +0000, Moore, Robert wrote:
> I don’t have any problem changing this in ACPICA if/when you all agree.
Great. I will resend this patch alone, assuming the patch can be based on
the Dan's NVDIMM tree (since it changes NFIT files).
Thanks,
-Toshi
next prev parent reply other threads:[~2015-08-27 14:34 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
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 [this message]
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=1440685923.14237.89.camel@hp.com \
--to=toshi.kani@hp.com \
--cc=dan.j.williams@intel.com \
--cc=david.e.box@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=rafael@kernel.org \
--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 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.