[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10189900.qsvQBSpnvI@vostro.rjw.lan>
Date: Tue, 18 Jun 2013 02:42:13 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Matthew Garrett <matthew.garrett@...ula.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"seth.forshee@...onical.com" <seth.forshee@...onical.com>,
"joeyli.kernel@...il.com" <joeyli.kernel@...il.com>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"lenb@...nel.org" <lenb@...nel.org>,
Bob Moore <robert.moore@...el.com>
Subject: Re: [PATCH 2/3] ACPICA: Add interface for getting latest OS version requested via _OSI
On Monday, June 17, 2013 10:37:10 PM Matthew Garrett wrote:
> On Tue, 2013-06-18 at 00:31 +0200, Rafael J. Wysocki wrote:
> > Hi Matthew,
> >
> > On Sunday, June 09, 2013 07:01:38 PM Matthew Garrett wrote:
> > > Drivers may need to make policy decisions based on the OS that the firmware
> > > believes it's interacting with. ACPI firmware will make a series of _OSI
> > > calls, starting from the oldest OS version they support and ending with the
> > > most recent. Add a function to return the last successful call so that
> > > drivers know what the firmware's expecting.
> > >
> > > Based on a patch by Seth Forshee <seth.forshee@...onical.com>
> >
> > Bob (CCed) would prefer us to access acpi_gbl_osi_data directly instead of
> > adding the wrapper to ACPICA. He also thinks that the symbol definitions
> > should go into include/acpi/actypes.h rather than into acpixf.h.
> >
> > Then, the only ACPICA change would be to move the symbols and we can
> > add a Linux-specific patch on top of that adding the acpi_gbl_osi_data
> > wrapper.
>
> That sounds good to me. Do you want to respin that, or should I send an
> updated set?
That one should be fine, no need to respin [1/3] and [3/3].
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists