From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Zheng, Lv" <lv.zheng@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, yinghai@kernel.org, bhe@redhat.com,
bp@alien8.de, fengguang.wu@intel.com
Subject: Re: [PATCH v9] ACPI / init: Invoke early ACPI initialization earlier
Date: Wed, 27 Sep 2017 07:33:54 +0000 [thread overview]
Message-ID: <88ed94a1-83bb-0338-caaa-e1773812ce4a@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709270917590.1945@nanos>
Hi Thomas,
At 09/27/2017 03:19 PM, Thomas Gleixner wrote:
> On Wed, 27 Sep 2017, Dou Liyang wrote:
>
>> Hi Rafael, Zheng,
>>
>> Welcome any comments!
>>
>> Now, our patches are in tip tree, they are based on this
>> independent patch, we hope it can be merged earlier than our
>> patches to avoid ACPI Error. we need your advice and confirmation.
>
> You should have included that patch into your APIC series so I would have
> been aware that it's required for the APIC changes to work on all
> platforms.
>
> But not a big problem. I merge it through tip/x86/apic so the stuff works
> as expected.
>
Yeah, thank you so much.
Thanks,
dou.
next prev parent reply other threads:[~2017-09-27 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1505293975-26005-1-git-send-email-douly.fnst@cn.fujitsu.com>
2017-09-13 9:17 ` [PATCH v9] ACPI / init: Invoke early ACPI initialization earlier Dou Liyang
2017-09-27 1:41 ` Dou Liyang
2017-09-27 7:19 ` Thomas Gleixner
2017-09-27 7:33 ` Dou Liyang [this message]
2017-09-27 9:02 ` Borislav Petkov
2017-09-27 10:06 ` Dou Liyang
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=88ed94a1-83bb-0338-caaa-e1773812ce4a@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=yinghai@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