From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kmemleak: Pull request
Date: Fri, 12 Jun 2009 10:53:26 +0100 [thread overview]
Message-ID: <1244800406.26670.29.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0906111420430.3535@localhost.localdomain>
On Thu, 2009-06-11 at 14:21 -0700, Linus Torvalds wrote:
>
> On Thu, 11 Jun 2009, Catalin Marinas wrote:
> >
> > Please consider pulling the kmemleak patches from the branch detailed
> > below.
>
> Ok, I got conflicts with the slab/earlyboot changes, but they looked
> resolvable. I haven't tested the merge though, so please do give it a good
> check.
I tested it with both slab and slub allocators and seems alright (and
found a possible leak in tty_ldisc.c). I'll give it a try with slob as
well.
There are two more trivial patches to merge. I'll send them as replies
to this mail but you can pull them directly from the same for-linus
branch:
The following changes since commit 8ebf975608aaebd7feb33d77f07ba21a6380e086:
Randy Dunlap (1):
block: fix kernel-doc in recent block/ changes
are available in the git repository at:
git://linux-arm.org/linux-2.6.git for-linus
Catalin Marinas (2):
kmemleak: Remove the kmemleak.h include in drivers/char/vt.c
kmemleak: Add more info to the MAINTAINERS entry
MAINTAINERS | 16 ++++++++++------
drivers/char/vt.c | 1 -
2 files changed, 10 insertions(+), 7 deletions(-)
Thanks.
--
Catalin
next prev parent reply other threads:[~2009-06-12 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 16:25 Catalin Marinas
2009-06-11 21:21 ` Linus Torvalds
2009-06-12 9:53 ` Catalin Marinas [this message]
2009-06-12 9:55 ` [PATCH 1/2] kmemleak: Remove the kmemleak.h include in drivers/char/vt.c Catalin Marinas
2009-06-12 12:07 ` Alan Cox
2009-06-12 9:55 ` [PATCH 2/2] kmemleak: Add more info to the MAINTAINERS entry 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=1244800406.26670.29.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®