linux-kernel - New rt-tests maintainer

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>] [day] [month] [year] [list]

Date:	Mon, 13 Oct 2008 22:23:18 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	rt-users <linux-rt-users@...r.kernel.org>
cc:	Clark Williams <williams@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Carsten Emde <ce@...g.ch>, LKML <linux-kernel@...r.kernel.org>
Subject: New rt-tests maintainer

Hi everyone,

I'm handing over the maintainership of rt-tests (cyclictest,
signaltest, pi_stress) to Clark Williams.

rt-tests started with cyclictest, a test program I wrote for
validating the high resolution timers implementation. In hindsight I'm
still surprised that cyclictest became a defacto standard for
benchmarking preempt-rt, but on the technical side it's quite clear as
it tests the whole chain: interrupt -> wakeup -> scheduler ->
userspace.

I never expected that cyclictest might ship with distros and I'm very
grateful to all the people who contributed and helped to bring it and
the whole rt-tests package into shape. I know that I'm a lousy user
space programmer :)

@Clark, thanks for taking over. It takes away my permanent guilty
conscience of not caring about rt-tests enough.

@all, please support Clark with his new project as you supported
me. Thanks for all the support and help again !

Thanks,

	tglx

P.S.: If you really need to add autocrap^H^H^H^Htools please do it in
      a way so I still can hack on it :)
--
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/