From: Andrew Morton <akpm@linux-foundation.org>
To: Robin Holt <holt@sgi.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
linux-mm@kvack.org, Avi Kivity <avi@redhat.com>,
Hugh Dickins <hughd@google.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Sagi Grimberg <sagig@mellanox.co.il>,
Haggai Eran <haggaie@mellanox.com>,
stable-kernel <stable@vger.kernel.org>
Subject: Re: [PATCH] mmu_notifier_unregister NULL Pointer deref and multiple ->release() callouts. [V2]
Date: Mon, 4 Feb 2013 14:18:54 -0800 [thread overview]
Message-ID: <20130204141854.b13973d2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20130204130306.GL3438@sgi.com>
On Mon, 4 Feb 2013 07:03:06 -0600
Robin Holt <holt@sgi.com> wrote:
>
> Cc: stable-kernel <stable@vger.kernel.org> # 3.[0-6].y 21a9273
> Cc: stable-kernel <stable@vger.kernel.org> # 3.[0-6].y 7040030
> Cc: stable-kernel <stable@vger.kernel.org>
>
> ...
>
> Andrew, I have a question about the stable maintainer bits I hope you
> could help me with. Will the syntax I used above get this into 3.0.y
> through 3.7.y? 3.7.y does not need the other two commits, but all the
> rest do. If not and you wouldn't mind fixing it up for me, I would
> appreciate the help.
um, I'd fix it up if I understood it, but I'm not sure that I do with
sufficient reliability.
If you want to send a message like this to Greg and to others who
maintain earlier kernel versions then I suggest you just spell it all
out in plain old English in the main changelog. That's not very useful
information for people who are following mainline, but a couple
paragraphs in a changelog won't kill anyone.
So can you please send me those couple of paragraphs and I'll paste
them in there headlined "-stable suggestions".
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-04 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 13:03 Robin Holt
2013-02-04 22:18 ` Andrew Morton [this message]
2013-02-04 22:37 ` Robin Holt
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=20130204141854.b13973d2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=haggaie@mellanox.com \
--cc=holt@sgi.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=sagig@mellanox.co.il \
--cc=stable@vger.kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.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