[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACVXFVMgd9Jzsf-pyqt5+DmtXNeRjY1UuHC6DYg6Zk9rOc9dUw@mail.gmail.com>
Date: Sun, 2 Nov 2014 15:47:20 +0800
From: Ming Lei <ming.lei@...onical.com>
To: "Kweh, Hock Leong" <hock.leong.kweh@...el.com>
Cc: "Fleming, Matt" <matt.fleming@...el.com>,
Sam Protsenko <semen.protsenko@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>
Subject: Re: [PATCH v1 1/3] firmware loader: Introduce new API - request_firmware_abort()
On Wed, Oct 29, 2014 at 11:04 AM, Kweh, Hock Leong
<hock.leong.kweh@...el.com> wrote:
>> -----Original Message-----
>> From: Ming Lei [mailto:ming.lei@...onical.com]
>> Sent: Monday, October 27, 2014 12:00 AM
>>
>> You can call fw_lookup_buf() directly, otherwise feel free to add:
>>
>> Acked-by: Ming Lei <ming.lei@...onical.com>
>>
>
> Hi Ming Lei,
>
> The fw_lookup_buf() is defined inside the conditional preprocessor directive for CONFIG_PM_SLEEP.
> Since the request_firmware_abort() may not only be used in PM_SLEEP, could I move the fw_lookup_buf()
> out from the CONFIG_PM_SLEEP block if we want to call fw_lookup_buf() instead of __fw_lookup_buf()?
Sure.
Thanks,
--
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