From: "Bobniev, Roman" <Roman.Bobniev@sonymobile.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"frowand.list@gmail.com" <frowand.list@gmail.com>,
"\"Andersson, Björn\"" <Bjorn.Andersson@sonymobile.com>,
"tbird20d@gmail.com" <tbird20d@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pekka Enberg" <penberg@kernel.org>,
"Bird, Tim" <Tim.Bird@sonymobile.com>,
"cl@linux.com" <cl@linux.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: RE: [PATCH] slub: proper kmemleak tracking if CONFIG_SLUB_DEBUG disabled
Date: Wed, 23 Oct 2013 13:52:19 +0200 [thread overview]
Message-ID: <F901C6708ADD5241BD39AFE3DD266906013746E21BDC@seldmbx01.corpusers.net> (raw)
In-Reply-To: <000001419e9e3e33-67807dca-e435-43ee-88bc-3ead54a83762-000000@email.amazonses.com>
> On Tue, 8 Oct 2013, Tim Bird wrote:
>
> > It also fixes a bug where kmemleak was only partially enabled in some
> > configurations.
>
> Acked-by: Christoph Lameter <cl@linux.com>
Could you help me, who the maintainer is that
puts this patch in a tree and pushes it to mainline?
Do we wait on some additional Ack from someone?
With best regards,
Roman.
--
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-10-23 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 22:58 Tim Bird
2013-10-09 13:28 ` Catalin Marinas
2013-10-09 19:07 ` Christoph Lameter
2013-10-23 11:52 ` Bobniev, Roman [this message]
2013-10-24 17:20 ` Pekka Enberg
-- strict thread matches above, loose matches on Subject: below --
2013-10-08 22:37 Tim Bird
2013-09-27 20:38 [PATCH] slub: Proper " Frank Rowand
2013-09-30 9:04 ` Catalin Marinas
2013-10-02 14:41 ` Christoph Lameter
2013-10-02 15:33 ` Bird, Tim
2013-10-02 15:54 ` Catalin Marinas
2013-10-02 16:24 ` Christoph Lameter
2013-10-02 15:57 ` Christoph Lameter
2013-10-02 16:25 ` Catalin Marinas
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=F901C6708ADD5241BD39AFE3DD266906013746E21BDC@seldmbx01.corpusers.net \
--to=roman.bobniev@sonymobile.com \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=tbird20d@gmail.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