| 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
| ||
|
Message-ID: <20060905150706.GB14242@mail1.bwalle.de> Date: Tue, 5 Sep 2006 17:07:06 +0200 From: Bernhard Walle <bernhard.walle@....de> To: linux-kernel@...r.kernel.org Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com> Subject: hrtimers -- high-resolution clock subsystem Hello, ,----[ Documentation/hrtimers.txt]-- | We used the high-resolution clock subsystem ontop of hrtimers to | verify the hrtimer implementation details in praxis `---- I didn't find any "high-resolution clock subsystem" in the internet as patch. Can you give me the point or did I got this sentence wrong? Thanks. BTW: There's a typo in this text, patch below. And I hope the patch is correct. Or would an extra email for this be better? ------------------------------------------------------------------------- Fixed typo in hrtimers documentation. Signed-off-by: Bernhard Walle <bernhard.walle@....de> --- hrtimers.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- Documentation/hrtimers.txt.orig 2006-09-05 16:53:51.000000000 +0200 +++ Documentation/hrtimers.txt 2006-09-05 16:54:48.000000000 +0200 @@ -149,7 +149,7 @@ ---------------------------------- We used the high-resolution clock subsystem ontop of hrtimers to verify -the hrtimer implementation details in praxis, and we also ran the posix +the hrtimer implementation details in practise, and we also ran the posix timer tests in order to ensure specification compliance. We also ran tests on low-resolution clocks. - 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