From: Hareesh Gundu <hareeshg@codeaurora.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>,
jcrouse@codeaurora.org, hareeshg@codeaurora.org,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] power: qos: Export pm_qos_update_request_timeout()
Date: Wed, 6 Dec 2017 21:05:39 +0530 [thread overview]
Message-ID: <38aa8cac-3e7b-8406-a8d0-ee13b35d4811@codeaurora.org> (raw)
In-Reply-To: <CAJZ5v0hwFo2hake52oGqrLt09ivfNCmw8pJY6uwqXVQ97FchkA@mail.gmail.com>
On 12/5/2017 8:54 PM, Rafael J. Wysocki wrote:
> On Tue, Dec 5, 2017 at 11:45 AM, Hareesh Gundu <hareeshg@codeaurora.org> wrote:
>> Add EXPORT_SYMBOL_GPL to pm_qos_update_request_timeout,
>> so that it can be usable from modules similar to the
>> pm_qos_update_request().
>>
>> Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
There is no in-tree kernel module using it. It's required for modules
built out-tree kernel.
Does it really required show out tree kernel module uses this symbol ?
> I'd rather see a modular user of this along with the export.
>
>> ---
>> kernel/power/qos.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel/power/qos.c b/kernel/power/qos.c
>> index 9d75039..3f501b4 100644
>> --- a/kernel/power/qos.c
>> +++ b/kernel/power/qos.c
>> @@ -515,6 +515,7 @@ void pm_qos_update_request_timeout(struct pm_qos_request *req, s32 new_value,
>>
>> schedule_delayed_work(&req->work, usecs_to_jiffies(timeout_us));
>> }
>> +EXPORT_SYMBOL_GPL(pm_qos_update_request_timeout);
>>
>> /**
>> * pm_qos_remove_request - modifies an existing qos request
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2017-12-06 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:45 [PATCH] power: qos: Export pm_qos_update_request_timeout() Hareesh Gundu
2017-12-05 15:24 ` Rafael J. Wysocki
2017-12-06 15:35 ` Hareesh Gundu [this message]
2017-12-06 16:43 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38aa8cac-3e7b-8406-a8d0-ee13b35d4811@codeaurora.org \
--to=hareeshg@codeaurora.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox