[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E37E4554A9@ORSMSX110.amr.corp.intel.com>
Date: Tue, 29 Mar 2016 17:50:00 +0000
From: "Moore, Robert" <robert.moore@...el.com>
To: Joe Perches <joe@...ches.com>, "Zheng, Lv" <lv.zheng@...el.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
Len Brown <lenb@...nel.org>
CC: "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"devel@...ica.org" <devel@...ica.org>
Subject: RE: [RFC PATCH] acpi: Use a more normal logging style for
ACPI_<LEVEL> calls
> -----Original Message-----
> From: Joe Perches [mailto:joe@...ches.com]
> Sent: Tuesday, March 29, 2016 9:57 AM
> To: Moore, Robert; Zheng, Lv; Wysocki, Rafael J; Len Brown
> Cc: linux-acpi@...r.kernel.org; linux-kernel; devel@...ica.org
> Subject: Re: [RFC PATCH] acpi: Use a more normal logging style for
> ACPI_<LEVEL> calls
>
> On Tue, 2016-03-29 at 15:34 +0000, Moore, Robert wrote:
> > On the other hand, we removed AE_INFO from ACPI_INFO a while back, and
> > this may remove the necessity for the double parens.
>
> Hmm, maybe not. It may be that MSVC's support for __VA_ARGS__ is a bit
> unusual. What's the minimum ACPICA msvc version required?
6 I think.
The AE_INFO automatically injects the module name, line number, etc.
Compatibility across compilers is a major requirement for us.
Powered by blists - more mailing lists