From: Eric Blake <eblake@redhat.com>
To: Liu Jingqi <jingqi.liu@intel.com>,
pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 1/7] hmat acpi: Build Memory Subsystem Address Range Structre(s) in ACPI HMAT
Date: Wed, 9 May 2018 08:13:02 -0500 [thread overview]
Message-ID: <5c500726-bd2d-2261-68ec-dd39c98d06aa@redhat.com> (raw)
In-Reply-To: <1525854869-13975-1-git-send-email-jingqi.liu@intel.com>
On 05/09/2018 03:34 AM, Liu Jingqi wrote:
In the subject line: s/Structre/Structure/
Long subject line; read 'git shortlog -30' to get a feel for more
typical subjects, and try to keep it at 60 characters or less (you still
want legible subjects in an 80-column window even when git adds
indentation and/or abbreviated commit id prefixes)
> HMAT is defined in ACPI 6.2: 5.2.27 Heterogeneous Memory Attribute Table (HMAT).
> The specification references below link:
> http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
Also, your mail was sent without any In-Reply-To: or References:
headers, meaning it was not threaded to a 0/7 cover letter, but instead
7 different top-level threads. That makes it harder to track replies to
your thread.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-05-09 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 8:34 [Qemu-devel] [PATCH v1 1/7] hmat acpi: Build Memory Subsystem Address Range Structre(s) in ACPI HMAT Liu Jingqi
2018-05-09 13:13 ` Eric Blake [this message]
2018-05-10 3:05 ` Liu, Jingqi
2018-05-11 14:40 ` Eduardo Habkost
2018-05-14 5:55 ` Liu, Jingqi
2018-05-15 14:35 ` Igor Mammedov
2018-05-16 6:28 ` Liu, Jingqi
2018-05-15 14:41 ` Igor Mammedov
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=5c500726-bd2d-2261-68ec-dd39c98d06aa@redhat.com \
--to=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.