From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, dm-devel@redhat.com,
linux-kernel@vger.kernel.org,
"Alasdair G. Kergon" <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: slab_common: fix the check for duplicate slab names
Date: Fri, 23 May 2014 16:16:33 -0400 [thread overview]
Message-ID: <20140523201632.GA16013@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1403251306260.26471@nuc>
On Tue, Mar 25 2014 at 2:07pm -0400,
Christoph Lameter <cl@linux.com> wrote:
> On Tue, 25 Mar 2014, Mike Snitzer wrote:
>
> > This patch still isn't upstream. Who should be shepherding it to Linus?
>
> Pekka usually does that.
>
> Acked-by: Christoph Lameter <cl@linux.com>
This still hasn't gotten upstream.
Pekka, any chance you can pick it up? Here it is in dm-devel's
kernel.org patchwork: https://patchwork.kernel.org/patch/3768901/
(Though it looks like it needs to be rebased due to the recent commit
794b1248, should Mikulas rebase and re-send?)
Mike
--
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:[~2014-05-23 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 22:13 [PATCH] slab_common: fix the check for duplicate slab names Mikulas Patocka
2014-03-04 22:48 ` David Rientjes
2014-03-25 17:03 ` Mike Snitzer
2014-03-25 18:07 ` Christoph Lameter
2014-05-23 20:16 ` Mike Snitzer [this message]
2014-05-23 21:28 ` Pekka Enberg
2014-05-24 0:37 ` Mike Snitzer
2014-07-22 22:14 ` Mike Snitzer
2014-07-22 22:41 ` [patch] " David Rientjes
2014-07-22 22:58 ` [git pull] stable mm/slab_common.c fix for 3.16-rc7 Mike Snitzer
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=20140523201632.GA16013@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=cl@linux.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpatocka@redhat.com \
--cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).