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: <Pine.LNX.4.44L0.1009171000100.1589-100000@iolanthe.rowland.org>
Date:	Fri, 17 Sep 2010 10:03:10 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Kevin Hilman <khilman@...prootsystems.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: PM / Wakeup: Introduce wakeup source objects and event statistics
 (v2)

On Fri, 17 Sep 2010, Rafael J. Wysocki wrote:

> > Was doing some experiments with this on OMAP, and found a minor
> > cut-and-paste bug in the Documentation file:
> > 
> > [...]
> > 
> > > +What:		/sys/devices/.../power/wakeup_max_time_ms
> > > +Date:		September 2010
> > > +Contact:	Rafael J. Wysocki <rjw@...k.pl>
> > > +Description:
> > > +		The /sys/devices/.../wakeup_max_time_ms attribute contains
> > > +		the maximum time of processing a single wakeup event associated
> > > +		with the device, in milliseconds.  This attribute is read-only.
> > > +		If the device is not enabled to wake up the system from sleep
> > > +		states, this attribute is empty.
> > > +
> > > +What:		/sys/devices/.../power/wakeup_max_time_ms
> >                                                       ^^^
> > s/max/last/ for this one.
> 
> Ah, thanks a lot.

There was another copy & paste errors in that file, a 
"wakeup_active_count" that should be "wakeup_hit_count".

Alan Stern

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