linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: James Morse <james.morse@arm.com>,
	Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
	<linux-acpi@vger.kernel.org>, Hanjun Guo <guohanjun@huawei.com>
Subject: [PATCH 0/9] ACPI: Call acpi_put_table() to release the ACPI table mappings
Date: Thu, 7 May 2020 17:09:12 +0800	[thread overview]
Message-ID: <1588842561-32907-1-git-send-email-guohanjun@huawei.com> (raw)

The acpi_get_table() should be coupled with acpi_put_table() if the
mapped table is not used for runtime after the initialization, or the
error path or the initialization, to release the table mapping.

This patchset just scan for every acpi_get_table() in ACPI subsystem to
see if acpi_put_table() is needed, this is not urgent and I think can
be merged for 5.8 if this patchset makes sense.

Hanjun Guo (9):
  ACPI: LPIT: Put the low power idle table after using it
  ACPI: watchdog: Put the watchdog action table after parsing
  ACPI: APEI: Put the boot error record table after parsing
  ACPI: APEI: Put the error injection table for error path and module
    exit
  ACPI: APEI: Put the error record serialization table for error path
  ACPI: APEI: Put the HEST table for error path
  ACPI: EC: Put the ACPI table after using it
  ACPI: scan: Put SPCR and STAO table after using it
  ACPI: sleep: Put the FACS table after using it

 drivers/acpi/acpi_lpit.c     |  3 ++-
 drivers/acpi/acpi_watchdog.c |  7 +++++--
 drivers/acpi/apei/bert.c     |  6 ++++--
 drivers/acpi/apei/einj.c     |  5 ++++-
 drivers/acpi/apei/erst.c     |  4 +++-
 drivers/acpi/apei/hest.c     |  5 +++--
 drivers/acpi/ec.c            | 14 ++++++++++----
 drivers/acpi/scan.c          | 15 ++++++++++-----
 drivers/acpi/sleep.c         |  4 +++-
 9 files changed, 44 insertions(+), 19 deletions(-)

-- 
1.7.12.4


             reply	other threads:[~2020-05-07  9:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  9:09 Hanjun Guo [this message]
2020-05-07  9:09 ` [PATCH 1/9] ACPI: LPIT: Put the low power idle table after using it Hanjun Guo
2020-05-07  9:09 ` [PATCH 2/9] ACPI: watchdog: Put the watchdog action table after parsing Hanjun Guo
2020-05-07  9:09 ` [PATCH 3/9] ACPI: APEI: Put the boot error record " Hanjun Guo
2020-05-07  9:09 ` [PATCH 4/9] ACPI: APEI: Put the error injection table for error path and module exit Hanjun Guo
2020-05-07  9:09 ` [PATCH 5/9] ACPI: APEI: Put the error record serialization table for error path Hanjun Guo
2020-05-07  9:09 ` [PATCH 6/9] ACPI: APEI: Put the HEST " Hanjun Guo
2020-05-07  9:09 ` [PATCH 7/9] ACPI: EC: Put the ACPI table after using it Hanjun Guo
2020-05-09  9:11   ` Rafael J. Wysocki
2020-05-09  9:30     ` Rafael J. Wysocki
2020-05-09  9:47       ` Hanjun Guo
2020-05-07  9:09 ` [PATCH 8/9] ACPI: scan: Put SPCR and STAO " Hanjun Guo
2020-05-07  9:09 ` [PATCH 9/9] ACPI: sleep: Put the FACS " Hanjun Guo

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=1588842561-32907-1-git-send-email-guohanjun@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tony.luck@intel.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 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).