From: J Freyensee <james_p_freyensee@linux.intel.com>
To: David Rientjes <rientjes@google.com>
Cc: gregkh@suse.de, 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: Thu, 05 May 2011 09:59:36 -0700 [thread overview]
Message-ID: <1304614776.8860.51.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.1104251357260.31884@chino.kir.corp.google.com>
On Mon, 2011-04-25 at 13:57 -0700, David Rientjes wrote:
> On Fri, 22 Apr 2011, 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>
>
> Third time:
>
> Acked-by: David Rientjes <rientjes@google.com>
Okay, so you want me to add an 'acked-by' next time on this patch in my
patch-set series?
next prev parent reply other threads:[~2011-05-05 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 23:32 [PATCH 1/4] export kernel call get_task_comm() james_p_freyensee
2011-04-25 20:57 ` David Rientjes
2011-05-05 16:59 ` J Freyensee [this message]
2011-05-05 18:55 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2011-05-06 23:56 james_p_freyensee
2011-04-19 22:58 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
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
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=1304614776.8860.51.camel@localhost \
--to=james_p_freyensee@linux.intel.com \
--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 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.