From: Andy Lutomirski <luto@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 3/3] dev_pm_qos: Export dev_pm_qos_update_user_latency_tolerance
Date: Tue, 29 Nov 2016 17:11:52 -0800 [thread overview]
Message-ID: <9cee8760c35e7eae1d85de83c5217fd3eb0f18f0.1480468027.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1480468027.git.luto@kernel.org>
In-Reply-To: <cover.1480468027.git.luto@kernel.org>
nvme wants a module parameter that overrides the default latency
tolerance. This makes it easy for nvme to reflect that default in
sysfs.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
drivers/base/power/qos.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/power/qos.c b/drivers/base/power/qos.c
index 6a1f2c7e01ea..58fcc758334e 100644
--- a/drivers/base/power/qos.c
+++ b/drivers/base/power/qos.c
@@ -886,6 +886,7 @@ int dev_pm_qos_update_user_latency_tolerance(struct device *dev, s32 val)
mutex_unlock(&dev_pm_qos_mtx);
return ret;
}
+EXPORT_SYMBOL_GPL(dev_pm_qos_update_user_latency_tolerance);
/**
* dev_pm_qos_expose_latency_tolerance - Expose latency tolerance to userspace
--
2.9.3
next prev parent reply other threads:[~2016-11-30 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 1:11 [PATCH 0/3] dev_pm_qos improvements Andy Lutomirski
2016-11-30 1:11 ` [PATCH 1/3] dev_pm_qos: Improve sysfs pm_qos_latency_tolerance validation Andy Lutomirski
2016-12-05 11:19 ` Pavel Machek
2016-11-30 1:11 ` [PATCH 2/3] dev_pm_qos: Fix writing 'auto' to pm_qos_latency_tolerance_us Andy Lutomirski
2016-11-30 1:11 ` Andy Lutomirski [this message]
2016-12-01 14:26 ` [PATCH 0/3] dev_pm_qos improvements 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=9cee8760c35e7eae1d85de83c5217fd3eb0f18f0.1480468027.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).