From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <x86@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Cc: <rjw@rjwysocki.net>, <len.brown@intel.com>, <pavel@ucw.cz>,
<tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>
Subject: Re: [RFC PATCH 0/2] x86/boot: early ACPI MADT processing cleanup
Date: Wed, 19 Feb 2020 15:32:35 +0800 [thread overview]
Message-ID: <ea435734-c18d-b6b9-a729-e0c5e6e62991@cn.fujitsu.com> (raw)
In-Reply-To: <20200123014144.19155-1-caoj.fnst@cn.fujitsu.com>
Ping.
On 1/23/20 9:41 AM, Cao jin wrote:
> Logic in early_acpi_process_madt() & acpi_process_madt() is really hard to
> follow now. Clean them up.
>
> Done basic boot test on my x86-64 PC.
>
> CCed linux-acpi@vger.kernel.org
>
> Cao jin (2):
> x86/acpi: Improve code readablity of early madt processing
> x86/acpi: Cleanup acpi_process_madt()
>
> arch/x86/kernel/acpi/boot.c | 72 +++++++++++++++----------------------
> 1 file changed, 28 insertions(+), 44 deletions(-)
>
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2020-02-19 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 1:41 [RFC PATCH 0/2] x86/boot: early ACPI MADT processing cleanup Cao jin
2020-01-23 1:41 ` [RFC PATCH 1/2] x86/acpi: Improve code readablity of early madt processing Cao jin
2020-02-24 13:21 ` Borislav Petkov
2020-02-25 7:02 ` Cao jin
2020-03-16 9:20 ` Cao jin
2020-01-23 1:41 ` [RFC PATCH 2/2] x86/acpi: Cleanup acpi_process_madt() Cao jin
2020-02-19 7:32 ` Cao jin [this message]
2020-03-27 12:30 ` [RFC PATCH 0/2] x86/boot: early ACPI MADT processing cleanup Cao jin
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=ea435734-c18d-b6b9-a729-e0c5e6e62991@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@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).