From: Laszlo Ersek <lersek@redhat.com>
To: mst@redhat.com
Cc: Igor Mammedov <imammedo@redhat.com>,
philmd@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] acpi: cpuhp: document CPHP_GET_CPU_ID_CMD command
Date: Wed, 12 Feb 2020 23:27:34 +0100 [thread overview]
Message-ID: <3c6d3232-f5d3-3d42-da19-2aa5a3c7ef02@redhat.com> (raw)
In-Reply-To: <1580306781-228371-1-git-send-email-imammedo@redhat.com>
Michael,
On 01/29/20 15:06, Igor Mammedov wrote:
> Commit 3a61c8db9d25 introduced CPHP_GET_CPU_ID_CMD command but
> did not sufficiently describe it. Fix it by adding missing command
> documentation.
>
> Fixes: 3a61c8db9d25 ("acpi: cpuhp: add CPHP_GET_CPU_ID_CMD command")
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> ---
> docs/specs/acpi_cpu_hotplug.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/docs/specs/acpi_cpu_hotplug.txt b/docs/specs/acpi_cpu_hotplug.txt
> index a8ce5e7..9bb22d1 100644
> --- a/docs/specs/acpi_cpu_hotplug.txt
> +++ b/docs/specs/acpi_cpu_hotplug.txt
> @@ -94,6 +94,8 @@ write access:
> register in QEMU
> 2: following writes to 'Command data' register set OST status
> register in QEMU
> + 3: following reads from 'Command data' and 'Command data 2' return
> + architecture specific CPU ID value for currently selected CPU.
> other values: reserved
> [0x6-0x7] reserved
> [0x8] Command data: (DWORD access)
>
can you please merge this?
It's a docs patch, but 3a61c8db9d25 (noted in "Fixes:") had gone in
through your tree.
Thank you!
Laszlo
next prev parent reply other threads:[~2020-02-12 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 14:06 [PATCH] acpi: cpuhp: document CPHP_GET_CPU_ID_CMD command Igor Mammedov
2020-01-29 16:05 ` Laszlo Ersek
2020-02-12 22:27 ` Laszlo Ersek [this message]
2020-02-13 10:01 ` Michael S. Tsirkin
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=3c6d3232-f5d3-3d42-da19-2aa5a3c7ef02@redhat.com \
--to=lersek@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).