All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: xiaobing.tu@intel.com, ccross@android.com, davej@redhat.com,
	akpm@linux-foundation.org, mingo@elte.hu, rusty@rustcorp.com.au,
	a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, di.zhang@intel.com, xindong.ma@intel.com,
	alex.zuo@intel.com
Subject: Re: [PATCH 1/2] Staging: android: binder: Fix memory leak on thread/process exit
Date: Mon, 22 Oct 2012 13:00:47 -0700	[thread overview]
Message-ID: <20121022200047.GA18175@kroah.com> (raw)
In-Reply-To: <CAMP5XgfVPeN8CRwKxeTv6fL8M0MXV56R+GrWw88caVZrQfu+Vg@mail.gmail.com>

On Tue, Oct 16, 2012 at 03:45:20PM -0700, Arve Hjønnevåg wrote:
> On Tue, Oct 16, 2012 at 12:11 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Oct 15, 2012 at 05:32:41PM -0700, Arve Hjønnevåg wrote:
> >> If a thread or process exited while a reply, one-way transaction or
> >> death notification was pending, the struct holding the pending work
> >> was leaked.
> >>
> >> Change-Id: I2eaafaba1c0ecda3ec0872d449dc16d0721c21e7
> >
> > What is this field?  Please don't include this in kernel patches, it
> > forces me to edit the patch by hand :(
> >
> 
> It is a tag generated a git hook to uniquely identify a change through
> multiple revisions of that change. If the tag does not already exist
> the hook adds it. I removed it from the reposted patches as you
> requested, but have you considered leaving it in? It is a useful
> search token both for finding different revisions of a patch and for
> finding which branch a change has been cherry-picked into.

Sorry, I was being facetious, I knew what it really was, but the point
was, why would I?

As has been stated before, you can include information like this in your
patch, but you MUST reference it properly so that others can be able to
figure out what you mean.  A random Change-Id value means nothing given
that lots of different groups use gerrit.  You need a url, or a pointer
to which gerrit instance this refers to before you can include it.

Same goes for bugzilla entries, if you look in the kernel changelog, we
reference lots of different ones, but we use urls to determine which one
we are talking about (suse, red hat, kernel.org, etc.)

thanks,

greg k-h

  reply	other threads:[~2012-10-22 20:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  7:03 Fix memory leak in binder Tu, Xiaobing
2012-10-15  7:20 ` Fix memory leak in binder--version2 Tu, Xiaobing
2012-10-15 22:52   ` Greg KH
2012-10-15 23:55     ` Arve Hjønnevåg
2012-10-15 23:58       ` Greg KH
2012-10-16  0:32         ` [PATCH 1/2] Staging: android: binder: Fix memory leak on thread/process exit Arve Hjønnevåg
2012-10-16  0:32           ` [PATCH 2/2] Staging: android: binder: Allow using highmem for binder buffers Arve Hjønnevåg
2012-10-16  7:12             ` Greg KH
2012-10-16  7:11           ` [PATCH 1/2] Staging: android: binder: Fix memory leak on thread/process exit Greg KH
2012-10-16 22:45             ` Arve Hjønnevåg
2012-10-22 20:00               ` Greg KH [this message]
2012-10-23  0:58                 ` Arve Hjønnevåg
2012-10-23  3:12                   ` Greg KH
2012-10-16  0:39         ` Fix memory leak in binder--version2 Arve Hjønnevåg
2012-10-16  7:11           ` Greg KH
2012-10-16 22:29             ` [PATCH 1/4] Staging: android: binder: Add some missing binder_stat_br calls Arve Hjønnevåg
2012-10-16 22:29               ` [PATCH 2/4] Staging: android: binder: Add some tracepoints Arve Hjønnevåg
2012-10-16 22:29               ` [PATCH 3/4] Staging: android: binder: Fix memory leak on thread/process exit Arve Hjønnevåg
2012-10-16 22:29               ` [PATCH 4/4] Staging: android: binder: Allow using highmem for binder buffers Arve Hjønnevåg
2012-10-16 22:33             ` Fix memory leak in binder--version2 Arve Hjønnevåg

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=20121022200047.GA18175@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alex.zuo@intel.com \
    --cc=arve@android.com \
    --cc=ccross@android.com \
    --cc=davej@redhat.com \
    --cc=di.zhang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=xiaobing.tu@intel.com \
    --cc=xindong.ma@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.