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: <A5FE05C4C76E4C4CAB15D9962B96FC950C9A7A6431@orsmsx510.amr.corp.intel.com>
Date:	Fri, 19 Mar 2010 15:53:07 -0700
From:	"Othman, Ossama" <ossama.othman@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>, Greg KH <gregkh@...e.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: RE: [PATCH] Intel Restricted Access Region Handler

Andrew, Greg,

> Regarding the code itself: it appears to implement a userspace
> interface via some /dev node.  But there is no description of this
> interface at all in the changelog and there is no documentation
> provided.  But the userspace-facing interface is the most important
> part of the entire feature, because it is something we cannot ever
> change.  It should be exhaustively described right up-front in the
> changelog so that reviewers can easily and fully understand the
> proposed API.

Would a README file of some sort be suitable to describe the driver interface or should I just embed additional documentation in the driver's interface header?

Thanks,
-Ossama
--
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