From: Tao Xu <tao3.xu@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rafael.j.wysocki@intel.com, lenb@kernel.org,
dan.j.williams@intel.com, dave.hansen@linux.intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/HMAT: Fix the parsing of Cache Associativity and Write Policy
Date: Mon, 9 Dec 2019 16:38:39 +0800 [thread overview]
Message-ID: <ba82f0ed-16a9-8058-bc2c-560209750f0c@intel.com> (raw)
In-Reply-To: <20191209075517.GA691602@kroah.com>
On 12/9/2019 3:55 PM, Greg KH wrote:
> On Mon, Dec 09, 2019 at 03:43:21PM +0800, Tao Xu wrote:
>> Gentle ping :)
>>
>> On 12/2/2019 3:03 PM, Tao Xu wrote:
>>> In chapter 5.2.27.5, Table 5-147: Field "Cache Attributes" of
>>> ACPI 6.3 spec: 0 is "None", 1 is "Direct Mapped", 2 is "Complex Cache
>>> Indexing" for Cache Associativity; 0 is "None", 1 is "Write Back",
>>> 2 is "Write Through" for Write Policy.
>>>
>>> Signed-off-by: Tao Xu <tao3.xu@intel.com>
>>> ---
>>> drivers/acpi/numa/hmat.c | 4 ++--
>>> include/linux/node.h | 4 ++--
>>> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> It was the middle of the merge window that just ended a few hours ago.
> Please give maintainers a chance to catch up...
>
I understand, thanks
next prev parent reply other threads:[~2019-12-09 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 7:03 [PATCH] ACPI/HMAT: Fix the parsing of Cache Associativity and Write Policy Tao Xu
2019-12-09 7:43 ` Tao Xu
2019-12-09 7:55 ` Greg KH
2019-12-09 8:38 ` Tao Xu [this message]
2019-12-09 10:01 ` Rafael J. Wysocki
2019-12-10 1:04 ` Tao Xu
2019-12-10 8:06 ` Rafael J. Wysocki
2019-12-10 8:19 ` Tao Xu
2019-12-10 8:27 ` Rafael J. Wysocki
2019-12-10 13:18 ` Tao Xu
2019-12-11 3:04 ` Tao Xu
2019-12-11 3:37 ` Dan Williams
2019-12-11 4:27 ` Tao Xu
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=ba82f0ed-16a9-8058-bc2c-560209750f0c@intel.com \
--to=tao3.xu@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@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).