linux-kernel - Re: [RFC] maximum latency tracking infrastructure (version 2)

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]

Date:	Fri, 25 Aug 2006 12:35:42 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, len.brown@...el.com, mingo@...e.hu,
	akpm@...l.org, jbarnes@...tuousgeek.org, nickpiggin@...oo.com.au
Subject: Re: [RFC] maximum latency tracking infrastructure (version 2)

On Fri, 2006-08-25 at 21:26 +0200, Arjan van de Ven wrote:
> > 
> > The name space here is bugging me a little. Maybe prefix them with
> > "pm_latency" so you'd have "pm_latency_set_acceptable()" ,
> > "pm_latency_modify_acceptable()" , something like that. Likewise with
> > the file names , "include/linux/pm_latency.h"
> > 
> 
> there is no reason why this should JUST be about power management....

I'm just suggesting it would be nice to have a clear prefix on each
function. It's up to you what that prefix is.

Daniel

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