[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcuUTgVzT0ZTWfQDZOhdjVg8wp5UZC8UY0-eOvy0JVqNw@mail.gmail.com>
Date: Wed, 31 Jan 2018 17:41:27 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Juergen Gross <jgross@...e.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
xen-devel@...ts.xenproject.org, Len Brown <lenb@...nel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Ingo Molnar <mingo@...hat.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Stable <stable@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] x86/acpi: add retrieval function for rsdp address
On Mon, Jan 29, 2018 at 5:01 AM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Fri, Jan 26, 2018 at 7:08 PM, Andy Shevchenko
> <andy.shevchenko@...il.com> wrote:
>> I have stumbled on the similar stuff and realize that.
>>
>> Perhaps, one of the solution is to have an additional struct under
>> x86_init to alternate ACPI related stuff.
>
> I'm not sure if that really is a problem in this particular case.
>
> Why would you want to use different RSDP retrieval functions for one arch?
I was not clear. I'm talking about approach struct x86_init vs. __weak function.
In my case it has nothing to do with RDSP, but with ACPI stubs.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists