From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Greg KH <gregkh@suse.de>
Cc: akpm@linux-foundation.org, rientjes@google.com,
linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
christophe.guerard@intel.com
Subject: Re: [PATCH] export kernel call get_task_comm().
Date: Fri, 22 Apr 2011 15:59:42 -0700 [thread overview]
Message-ID: <1303513182.13457.134.camel@localhost> (raw)
In-Reply-To: <20110422224308.GA301@suse.de>
On Fri, 2011-04-22 at 15:43 -0700, Greg KH wrote:
> On Fri, Apr 22, 2011 at 03:35:44PM -0700, james_p_freyensee@linux.intel.com wrote:
> > 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>
>
> I think the goal is for the cleanup to happen now, to justify the
> addition of the exported symbol. Without that, there is no need to
> export the symbol now at all, as who knows when your driver will be
> accepted.
>
> Or, just wait and make it part of your driver patch series, like you did
> before, no need to get it accepted now, right?
>
Well, at some point a few people like Alan Cox and Arjan VdV would like
to see this work on it's way to Linus's tree.
I'll do whatever is best and easiest for you and will bring a close to
my submission attempts. I can also just go into the Kconfig where the
pti driver is configured and just make the selection bool, yes or no,
and not make it an option to compile this modularly. Then I'll drop
this patch all together. This is the whole reason why I'm making this
change. I don't have to have the pti driver as a module, just more
convenient. And within the fs/exec.c it states reads to 'current->comm'
without a lock is safe.
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2011-04-22 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 22:35 [PATCH] export kernel call get_task_comm() james_p_freyensee
2011-04-22 22:43 ` Greg KH
2011-04-22 22:59 ` J Freyensee [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-04-22 22:26 james_p_freyensee
2011-04-22 22:35 ` David Rientjes
2011-04-22 22:43 ` J Freyensee
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=1303513182.13457.134.camel@localhost \
--to=james_p_freyensee@linux.intel.com \
--cc=akpm@linux-foundation.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