From: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH] acpi: add NFIT and HMAT to the initrd override list
Date: Thu, 22 Feb 2018 14:12:24 -0700 [thread overview]
Message-ID: <20180222211224.GA29462@linux.intel.com> (raw)
In-Reply-To: <20171218195405.GA18900-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
On Mon, Dec 18, 2017 at 12:54:05PM -0700, Ross Zwisler wrote:
> On Fri, Dec 08, 2017 at 08:29:25AM -0800, Dan Williams wrote:
> > These tables, NFIT and HMAT, are essential for describing
> > next-generation platform memory topologies and performance
> > characteristics. Allow them to be overridden for debug and test and
> > purposes.
> >
> > Cc: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>
> Yes please! This works in my test setup for inserting custom HMAT tables, and
> I would really like to have this for testing my HMAT series:
>
> https://lists.01.org/pipermail/linux-nvdimm/2017-December/013571.html
>
> Reviewed-by: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>
> > Signed-off-by: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Ping on this patch - can we get this merged?
next prev parent reply other threads:[~2018-02-22 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 16:29 [PATCH] acpi: add NFIT and HMAT to the initrd override list Dan Williams
2017-12-18 19:54 ` Ross Zwisler
[not found] ` <20171218195405.GA18900-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-02-22 21:12 ` Ross Zwisler [this message]
[not found] ` <20180222211224.GA29462-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-02-22 21:47 ` Rafael J. Wysocki
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=20180222211224.GA29462@linux.intel.com \
--to=ross.zwisler-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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).