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: <20080707214905.157be089@infradead.org>
Date:	Mon, 7 Jul 2008 21:49:05 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	david@...g.hm
Cc:	"Altobelli, David" <david.altobelli@...com>,
	Pavel Machek <pavel@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"greg@...ah.com" <greg@...ah.com>
Subject: Re: [PATCH][resubmit] HP iLO driver

On Mon, 7 Jul 2008 21:41:41 -0700 (PDT)
david@...g.hm wrote:
> umm, by merging the code a you reveal a lot of what they are
> attempting to keep secret. what's to stop someone from reading the
> code and writing the documentation?
> 
> that really should be someone at HP if you don't want to publish the 
> exising documentation (since you are submitting the code)
> 

Hi,

I think you're being quite unreasonable here.
In Linux we accept well written drivers even if there is no hardware
docs. Sure we prefer them to be available, but is has never been a
requirement, nor should it. I know that some other open source OSes do
demand this, but Linux is not one of them. We explicitly accept drivers
written with NDA docs, or drivers written by vendors. 
It's the code that talks.
(and well written code is often worth more than the shoddy docs that we
sometimes get)

Greetings,
   Arjan van de Ven

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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