From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Erik Kaneda <erik.kaneda@intel.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/3] ACPICA release 20200717
Date: Mon, 27 Jul 2020 14:56:52 +0200 [thread overview]
Message-ID: <CAJZ5v0h2h6r5GW-+uT+HP6LZQpFtxjwhnSLAc=utQwF_FpU4AQ@mail.gmail.com> (raw)
In-Reply-To: <20200720173121.2580755-1-erik.kaneda@intel.com>
On Mon, Jul 20, 2020 at 7:55 PM Erik Kaneda <erik.kaneda@intel.com> wrote:
>
> This series contains patches relevant to linux kernel from ACPICA's
> 20200717 release. This ACPICA release contains a change in the ACPI
> object reference counting mechanism to allow firmware to declare a
> large amount of OperationRegion field units without overflowing the
> reference count.
>
> Bob Moore (1):
> ACPICA: Update version to 20200717 Version 20200717.
>
> Erik Kaneda (1):
> ACPICA: Do not increment operation_region reference counts for field
> units
>
> Gustavo A. R. Silva (1):
> ACPICA: Replace one-element array with flexible-array
>
> drivers/acpi/acpica/exprep.c | 4 ----
> drivers/acpi/acpica/utdelete.c | 6 +-----
> drivers/acpi/acpica/utids.c | 3 +--
> include/acpi/acpixf.h | 2 +-
> include/acpi/actypes.h | 2 +-
> 5 files changed, 4 insertions(+), 13 deletions(-)
>
> --
All three patches applied as 5.9 material, thanks!
prev parent reply other threads:[~2020-07-27 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:31 [PATCH 0/3] ACPICA release 20200717 Erik Kaneda
2020-07-20 17:31 ` [PATCH 1/3] ACPICA: Replace one-element array with flexible-array Erik Kaneda
2020-07-20 17:31 ` [PATCH 2/3] ACPICA: Do not increment operation_region reference counts for field units Erik Kaneda
2020-07-20 17:31 ` [PATCH 3/3] ACPICA: Update version to 20200717 Version 20200717 Erik Kaneda
2020-07-27 12:56 ` Rafael J. Wysocki [this message]
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='CAJZ5v0h2h6r5GW-+uT+HP6LZQpFtxjwhnSLAc=utQwF_FpU4AQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=erik.kaneda@intel.com \
--cc=linux-acpi@vger.kernel.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).