From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Shiju Jose <shiju.jose@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
<linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 4/5] acpi/generic_event_device: Update GHES migration to cover hest addr
Date: Mon, 25 Nov 2024 12:00:54 +0000 [thread overview]
Message-ID: <20241125120054.000036e8@huawei.com> (raw)
In-Reply-To: <9aa962a596769f5fa35c8af84b5a522cb12947f2.1732281080.git.mchehab+huawei@kernel.org>
On Fri, 22 Nov 2024 14:14:14 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> The GHES migration logic at GED should now support HEST table
> location too.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Not my area of expertise but looks sensible to me.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Shiju Jose <shiju.jose@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
<linux-kernel@vger.kernel.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 4/5] acpi/generic_event_device: Update GHES migration to cover hest addr
Date: Mon, 25 Nov 2024 12:00:54 +0000 [thread overview]
Message-ID: <20241125120054.000036e8@huawei.com> (raw)
In-Reply-To: <9aa962a596769f5fa35c8af84b5a522cb12947f2.1732281080.git.mchehab+huawei@kernel.org>
On Fri, 22 Nov 2024 14:14:14 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> The GHES migration logic at GED should now support HEST table
> location too.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Not my area of expertise but looks sensible to me.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2024-11-25 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 13:14 [PATCH v2 0/5] Change ghes driver to use HEST-based offsets Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 1/5] acpi/ghes: Prepare to support multiple sources on ghes Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 2/5] acpi/ghes: add a firmware file with HEST address Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 3/5] acpi/ghes: Use HEST table offsets when preparing GHES records Mauro Carvalho Chehab
2024-11-25 12:00 ` Jonathan Cameron
2024-11-25 12:00 ` Jonathan Cameron via
2024-11-22 13:14 ` [PATCH v2 4/5] acpi/generic_event_device: Update GHES migration to cover hest addr Mauro Carvalho Chehab
2024-11-25 12:00 ` Jonathan Cameron via [this message]
2024-11-25 12:00 ` Jonathan Cameron
2024-11-22 13:14 ` [PATCH v2 5/5] acpi/generic_event_device: add logic to detect if HEST addr is available Mauro Carvalho Chehab
2024-11-25 12:08 ` Jonathan Cameron
2024-11-25 12:08 ` Jonathan Cameron via
2024-12-03 12:03 ` [PATCH v2 0/5] Change ghes driver to use HEST-based offsets Igor Mammedov
2024-12-03 13:59 ` Mauro Carvalho Chehab
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=20241125120054.000036e8@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mst@redhat.com \
--cc=shiju.jose@huawei.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.