linux-kernel - Re: [PATCH 00/14] Kernel memory leak detector

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Jan 2009 14:50:02 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/14] Kernel memory leak detector

On Thu, 2009-01-15 at 01:01 +1100, Stephen Rothwell wrote:
> On Wed, 14 Jan 2009 12:30:20 +0000 Catalin Marinas <catalin.marinas@....com> wrote:
> > Are you OK with applying patches to linux-next (git am) rather than
> > using git merge? This way I can rebase kmemleak on top of linux-next.
> 
> I would much prefer a few conflicts to carrying a post linux-next patch
> because linux-next can change radically day to day - especially since we
> know there will be clashes in the areas of files you would be patching.
> 
> So lets use the above git tree and see how we go. OK?

It sounds fine. Thanks.

-- 
Catalin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/