[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gP4uWs8ka8SUGzxJ9GcRKdMiRMpc+OktBTHtug9MAdBw@mail.gmail.com>
Date: Thu, 17 Mar 2016 14:00:46 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
David Daney <ddaney.cavm@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Robert Richter <rrichter@...ium.com>,
Tomasz Nowicki <tn@...ihalf.com>,
David Daney <david.daney@...ium.com>
Subject: Re: [PATCH] ACPI / property: Export a couple of symbols.
On Thu, Mar 17, 2016 at 9:09 AM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:
> On Wed, Mar 16, 2016 at 05:23:19PM -0700, David Daney wrote:
>> From: David Daney <david.daney@...ium.com>
>>
>> The acpi_dev_prop_read() and acpi_dev_prop_read_single() can be called
>> by drivers. Add EXPORT_SYMBOL_GPL to them to allow use by modular
>> drivers. This makes them consistent with acpi_dev_get_property() and
>> acpi_node_get_property_reference() which are already exported.
>>
>> Signed-off-by: David Daney <david.daney@...ium.com>
>> ---
>> FWIW: We hope to submit soon Cavium Thunder networking patches that
>> fail under modular builds without these exports.
>
> You should not be using these functions directly in drivers.
That's exactly my point.
Powered by blists - more mailing lists