public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamal Mostafa <kamal@canonical.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Li Zefan <lizefan@huawei.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Hugh Dickins <hughd@google.com>, Tejun Heo <tj@kernel.org>,
	Glauber Costa <glommer@openvz.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	kernel-team@lists.ubuntu.com, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [ 3.8.y.z extended stable ] Patch "memcg, kmem: fix reference count handling on the error path" has been added to staging queue
Date: Tue, 16 Jul 2013 16:40:09 -0700	[thread overview]
Message-ID: <1374018009.3225.123.camel@fourier> (raw)
In-Reply-To: <20130716160658.fc30d70b5230aab5b3b3950b@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Tue, 2013-07-16 at 16:06 -0700, Andrew Morton wrote:
> On Tue, 16 Jul 2013 15:54:02 -0700 Kamal Mostafa <kamal@canonical.com> wrote:
> 
> > This is a note to let you know that I have just added a patch titled
> > 
> >     memcg, kmem: fix reference count handling on the error path
> > 
> > to the linux-3.8.y-queue branch of the 3.8.y.z extended stable tree 
> > which can be found at:
> 
> hm, why.

Because it said "Cc: <stable@vger.kernel.org> [3.8]", making me think
the author specifically wanted it to be applied to 3.8-stable.

>[...]
> Note to stable tree maintainers: I carefully evaluate every patch I
> handle to decide whether or not it should be backported.  Every single
> one.

Might you consider stripping off the "Cc: stable [3.8]" line when you
add your SOB, in such a case?

> Hence if you decide to backport a patch which I merged, you are
> overriding an earlier decision of mine.

I'm happy to defer to your judgment here.  I've dropped it from the
linux-3.8.y-queue.

> Now, I will freely admit that I may have made a mistake.  But please be
> aware that you are taking a path which I have already considered and
> rejected.  So a little extra care is warranted for akpm patches, please.

I'll try to watch out for them.

Thanks Andrew,

 -Kamal


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-16 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374015242-28112-1-git-send-email-kamal@canonical.com>
2013-07-16 23:06 ` [ 3.8.y.z extended stable ] Patch "memcg, kmem: fix reference count handling on the error path" has been added to staging queue Andrew Morton
2013-07-16 23:40   ` Kamal Mostafa [this message]
2013-07-17  0:45     ` Andrew Morton
2013-07-17  6:25       ` Li Zefan
2013-07-17  9:20         ` Michal Hocko

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=1374018009.3225.123.camel@fourier \
    --to=kamal@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@openvz.org \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mhocko@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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