linux-kernel - Re: [PATCH 2/2] lockdep: choose to continue lock debugging despite taint

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]

Message-ID: <20090412140919.GE5246@elte.hu>
Date:	Sun, 12 Apr 2009 16:09:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Greg KH <gregkh@...e.de>, LKML <linux-kernel@...r.kernel.org>,
	LTP <ltp-list@...ts.sourceforge.net>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 2/2] lockdep: choose to continue lock debugging despite
	taint


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> > Side request: do you think you could merge them on kill-the-BKL 
> > tree?
> 
> Sorry, forget about this side request. I thought merging 
> tip:master into tip:core/kill-the-BKL would make me suffer a rain 
> of conflicts but actually I've just tried and I only encountered a 
> very simple conflict in sched.c so it's very easy to manage it 
> locally. Then we can keep the history of kill-the-BKL, for now 
> it's good as is.

Ok - that's how we like topics anyway: as independent trees which 
happen to be mostly conflict-free when merged into tip:master.

	Ingo
--
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/