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: <57C9024A16AD2D4C97DC78E552063EA3061C5FA5@orsmsx505.amr.corp.intel.com>
Date:	Wed, 18 Jun 2008 10:15:27 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>,
	"ksummit-2008-discuss@...ts.linux-foundation.org" 
	<ksummit-2008-discuss@...ts.linux-foundation.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: RE: [Ksummit-2008-discuss] Request for discussion on when to merge
	drivers

> Experience has shown that for most SCSI drivers, the authors tend to be
> the people producing the hardware and without documentation, no-one else
> can fix up anything other than obvious coding errors, so we can't put it
> in the tree and hope someone else will fix it if they have a problem.

Is there an opportunity for a carrot here ... a driver submitted
*with documentation* gets a faster path into the tree?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ