linux-kernel - Re: [PATCH] maximum latency tracking infrastructure (version 3)

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: <200608280930.45273.jesse.barnes@intel.com>
Date:	Mon, 28 Aug 2006 09:30:45 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...l.org, mingo@...e.hu,
	dwalker@...sta.com
Subject: Re: [PATCH] maximum latency tracking infrastructure (version 3)

On Monday, August 28, 2006 9:25 am, Arjan van de Ven wrote:
> Jesse Barnes wrote:
> > On Monday, August 28, 2006 8:48 am, Arjan van de Ven wrote:
> >> 3rd version; only minor changes this time, the sysreq stuff is gone
> >> however.
> >>
> >> I've decided to not use a namespace prefix; these functions are
> >> meant to be generic,  and a namespace prefix is not common for such
> >> functions, and it would in addition cause a too narrow usage of
> >> this infrastructure.
> >
> > Almost forgot--what about documentation?  This is an addition to the
> > driver API, so it should probably be described clearly somewhere,
> > probably in Documentation/ somewhere...
>
> how about linuxdoc??

I like to have stuff in Documentation/ too, but if you think the existing 
function comments are good enough that's fine.

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