From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <gregkh@suse.de>
Cc: J Freyensee <james_p_freyensee@linux.intel.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
christophe.guerard@intel.com
Subject: Re: [PATCH 1/4] export kernel call get_task_comm().
Date: Wed, 20 Apr 2011 16:11:25 -0700 [thread overview]
Message-ID: <20110420161125.3449d4fd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110420191421.GA10306@suse.de>
On Wed, 20 Apr 2011 12:14:21 -0700
Greg KH <gregkh@suse.de> wrote:
> > But as David pointed out, if there is work other than mine coming that
> > has already been proposed, wouldn't it be good to get this patch in
> > place now to start the encouragement of future eyes to just call this
> > function than re-invent the wheel?
>
> No, then those projects submit the patch to export this, if they happen
> to get to mainline before this one does.
>
> Again, don't export something unless you are using it at the time, no
> "this is to be used hopefully by something in the future" type stuff
> please. Who knows if those future plans ever pan out.
Well there's an easy solution here. Send the patch to export
get_task_comm(), then send along some patches which fix
z:/usr/src/linux-2.6.39-rc4> grep -r 'current->comm' drivers | wc -l
89
next prev parent reply other threads:[~2011-04-20 23:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 22:58 [PATCH 1/4] export kernel call get_task_comm() james_p_freyensee
2011-04-19 23:22 ` David Rientjes
2011-04-20 0:10 ` J Freyensee
2011-04-20 1:22 ` David Rientjes
2011-04-20 1:43 ` Greg KH
2011-04-20 18:11 ` J Freyensee
2011-04-20 19:14 ` Greg KH
2011-04-20 23:11 ` Andrew Morton [this message]
2011-04-20 23:16 ` J Freyensee
2011-04-20 23:46 ` Andrew Morton
2011-04-21 16:12 ` J Freyensee
2011-04-20 23:19 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2011-04-22 23:32 james_p_freyensee
2011-04-25 20:57 ` David Rientjes
2011-05-05 16:59 ` J Freyensee
2011-05-05 18:55 ` David Rientjes
2011-05-06 23:56 james_p_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=20110420161125.3449d4fd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=christophe.guerard@intel.com \
--cc=gregkh@suse.de \
--cc=james_p_freyensee@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.