netdev - Re: pull request: wireless-next 2012-05-03

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: <20120503.132126.1970020317749906187.davem@davemloft.net>
Date:	Thu, 03 May 2012 13:21:26 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: pull request: wireless-next 2012-05-03

From: David Miller <davem@...emloft.net>
Date: Thu, 03 May 2012 13:17:07 -0400 (EDT)

> Really, we went through this a million times very recently and I'm
> not pulling anything into my tree that has garbage like this in it.

BTW, the bluetooth guys owe John Linville a serious apology.

Because of the crap situation they've created, I can no longer
trust John's pulls.

That means I have to baby-sit every pull request he sends me and
go through every single patch in it looking for these kinds of
problems.

This is _NOT_ how this is supposed to work.

John should be sending me things that are fully vetted and I can
basically trust to be in good shape.  But because of the bluetooth
guys that is not the case.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html