linux-kernel - Re: linux-next: build failure after merge of the scsi 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 for Android: free password hash cracker in your pocket

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

Message-ID: <4F6C9547.4060509@pobox.com>
Date:	Fri, 23 Mar 2012 11:22:47 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: linux-next: build failure after merge of the scsi tree

On 03/23/2012 05:01 AM, James Bottomley wrote:
> Yes, sorry ... it's one of those large all or nothing type series that
> touches about 33 different drivers (about 75% of which are
> unmaintained).

To be more specific, it was a patch series that was never CC'd to ANY 
driver author, nor linux-ide, nor LKML.

	Jeff


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