linux-kernel - Re: [PULL] bkl-removal tree

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] [day] [month] [year] [list]

Message-ID: <20080715161532.3fee41cb@bike.lwn.net>
Date:	Tue, 15 Jul 2008 16:15:32 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Christian Borntraeger <borntraeger@...ibm.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PULL] bkl-removal tree

On Tue, 15 Jul 2008 09:29:25 +0200
Christian Borntraeger <borntraeger@...ibm.com> wrote:

> Ok. Lets answer this question for anybody :-)
> I own this driver and I want to remove the BKL as soon as I am
> confident its ok. Should the followup patch be merged with Jonathans
> tree or should I sent it directly to Andrew or Linus?

I'll continue to maintain the bkl-removal tree, so you can certainly
send your patch meward and I'll herd it on upstream.  It's also OK to
send it up yourself or through a subsystem tree, of course.  I'm not
sure I'd bug Linus for detail stuff on this level...

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