From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lv Zheng <lv.zheng@intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ACPI / tables: Add table upgrade mechanism
Date: Thu, 21 Apr 2016 02:18:36 +0200 [thread overview]
Message-ID: <3948235.FadEB4uYLA@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1460340514.git.lv.zheng@intel.com>
On Monday, April 11, 2016 10:13:07 AM Lv Zheng wrote:
> This patch introduces a table upgrade mechanism based on the existing
> initrd table override mechanism.
>
> Updated due to a build error reported against early_acpi_table_init()
> stub.
>
> Lv Zheng (3):
> ACPI / tables: Move table override mechanisms to tables.c
> ACPI / x86: Cleanup initrd related code
> ACPI / tables: Convert the initrd table override mechanisms to the
> table upgrade mechanism
>
> Documentation/acpi/initrd_table_override.txt | 65 +++---
> arch/x86/kernel/setup.c | 12 +-
> drivers/acpi/Kconfig | 8 +-
> drivers/acpi/internal.h | 1 -
> drivers/acpi/osl.c | 274 ----------------------
> drivers/acpi/tables.c | 312 +++++++++++++++++++++++++-
> include/linux/acpi.h | 10 +-
> 7 files changed, 365 insertions(+), 317 deletions(-)
All [1-3/3] applied, thanks!
prev parent reply other threads:[~2016-04-21 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <273fd92043ff4972a71a94efdf01b67ee4638131>
2016-04-11 2:13 ` [PATCH v2 0/3] ACPI / tables: Add table upgrade mechanism Lv Zheng
2016-04-11 2:13 ` [PATCH v2 1/3] ACPI / tables: Move table override mechanisms to tables.c Lv Zheng
2016-04-11 2:13 ` [PATCH v2 2/3] ACPI / x86: Cleanup initrd related code Lv Zheng
2016-04-11 2:13 ` [PATCH v2 3/3] ACPI / tables: Convert the initrd table override mechanisms to the table upgrade mechanism Lv Zheng
2016-04-13 16:01 ` Octavian Purdila
2016-04-19 13:57 ` Octavian Purdila
2016-04-21 0:18 ` 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=3948235.FadEB4uYLA@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=zetalog@gmail.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).