linux-kernel - Re: [PATCH][resubmit] HP iLO driver

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: <20080708233417.6fff4672@the-village.bc.nu>
Date:	Tue, 8 Jul 2008 23:34:17 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Altobelli, David" <david.altobelli@...com>
Cc:	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

> Unfortunately, I don't believe that I can.  We reviewed this internally,
> and the question of documentation was raised.  The hardware teams did
> not approve disseminating the ABI.  To be clear, we understand what we

Well I suggest that when you've sorted out the internal politics in HP
*then* you resubmit the driver code with more info.

> > We are not _that_ extreme. Yes, keep stuff in userspace is important,
> > but "hide hardware differences" is more important goal.
> 
> That seems like a larger question/goal.  Giving users some consistent
> interfaces to do stuff would be nice, but I'd really like to handle this
> driver on its own.

We need to sort out the interface to merge a set of drivers and produce a
common sensible interface that exposes commonality properly. It's rather
hard to do that when you won't provide any relevant information.

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