linux-kernel - Re: [Ksummit-2008-discuss] Request for discussion on when to merge drivers

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: <1213810441.3515.73.camel@localhost.localdomain>
Date:	Wed, 18 Jun 2008 12:34:01 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	"ksummit-2008-discuss@...ts.linux-foundation.org" 
	<ksummit-2008-discuss@...ts.linux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Request for discussion on when to
	merge	drivers

On Wed, 2008-06-18 at 10:15 -0700, Luck, Tony wrote:
> > 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?

You mean with actual how to program it information?  er dunno ... never
seen one of those ...

But I suppose, theoretically, since anyone could access the
documentation to maintain it, it would be much more likely to be fixed
up in tree, yes.

James


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