public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com
To: akpm@linux-foundattion.org
Cc: rientjes@google.com, gregkh@suse.de,
	linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
	christophe.guerard@intel.com, james_p_freyensee@linux.intel.com
Subject: [PATCH] export kernel call get_task_comm().
Date: Fri, 22 Apr 2011 15:26:28 -0700	[thread overview]
Message-ID: <1303511188-728-2-git-send-email-james_p_freyensee@linux.intel.com> (raw)
In-Reply-To: <james_p_freyensee@linux.intel.com>

From: J Freyensee <james_p_freyensee@linux.intel.com>

This allows drivers who call this function to be compiled modularly.
Otherwise, a driver who is interested in this type of functionality
has to implement their own get_task_comm() call, causing code
duplication in the Linux source tree.

Signed-off-by: J Freyensee <james_p_freyensee@linux.intel.com>
---
 fs/exec.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/fs/exec.c b/fs/exec.c
index 8328beb..e1ac338 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -1004,6 +1004,7 @@ char *get_task_comm(char *buf, struct task_struct *tsk)
 	task_unlock(tsk);
 	return buf;
 }
+EXPORT_SYMBOL_GPL(get_task_comm);
 
 void set_task_comm(struct task_struct *tsk, char *buf)
 {
-- 
1.7.2.3


             reply	other threads:[~2011-04-22 22:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 22:26 james_p_freyensee [this message]
2011-04-22 22:35 ` [PATCH] export kernel call get_task_comm() David Rientjes
2011-04-22 22:43   ` J Freyensee
  -- strict thread matches above, loose matches on Subject: below --
2011-04-22 22:35 james_p_freyensee
2011-04-22 22:43 ` Greg KH
2011-04-22 22:59   ` J Freyensee
2011-04-22 23:04     ` Greg KH
2011-04-22 23:08       ` J Freyensee
2011-04-22 23:17         ` Greg KH
2011-04-22 23:19     ` David Rientjes

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=1303511188-728-2-git-send-email-james_p_freyensee@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    --cc=akpm@linux-foundattion.org \
    --cc=christophe.guerard@intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=suhail.ahmed@intel.com \
    /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