From: Pavel Roskin <proski@gnu.org>
To: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: [PATCH] sched: make task_nice available to non-GPL modules
Date: Wed, 05 Mar 2008 16:56:37 -0500 [thread overview]
Message-ID: <20080305215637.7767.99635.stgit@dv.roinet.com> (raw)
The API is trivial, and so is the implementation. Linux priorities are
exposed to the userspace, so nobody should claim that software aware of
Linux priorities is a derived work of the kernel.
The complementary function set_user_nice() is available to non-GPL
modules. If the module can set the priority, it should be able to read
it back.
Signed-off-by: Pavel Roskin <proski@gnu.org>
---
kernel/sched.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index dcd553c..6db6e0c 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -4422,7 +4422,7 @@ int task_nice(const struct task_struct *p)
{
return TASK_NICE(p);
}
-EXPORT_SYMBOL_GPL(task_nice);
+EXPORT_SYMBOL(task_nice);
/**
* idle_cpu - is a given cpu idle currently?
next reply other threads:[~2008-03-05 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 21:56 Pavel Roskin [this message]
2008-03-06 10:41 ` [PATCH] sched: make task_nice available to non-GPL modules Ingo Molnar
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=20080305215637.7767.99635.stgit@dv.roinet.com \
--to=proski@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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