| 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
| ||
|
Date: Sat, 2 Feb 2008 20:32:02 +0100 From: Pavel Machek <pavel@....cz> To: David Brownell <david-b@...bell.net> Cc: Ingo Molnar <mingo@...e.hu>, linux-pm@...ts.linux-foundation.org, kernel list <linux-kernel@...r.kernel.org> Subject: Re: [linux-pm] sleepy linux self-test On Sat 2008-02-02 11:13:21, David Brownell wrote: > On Saturday 02 February 2008, Ingo Molnar wrote: > > > > > > Yep, you are right, but that is the easy issue to fix. > > > > > > Which is why I was puzzled that you didn't start out doing it the > > > "right" way ... even just hard-wiring the dubious assumption that > > > "rtc0" is the right RTC to use. :) > > > > because this was mostly about an quick & easy hack to see whether it > > makes sense at all to automate the testing of suspend/resume. > > I think you should have written "quick and dirty". ;) > > It would have been easier to just use the public interface > and hard-wire "rtc0". But going directly to the hardware > was dirtier, and more in the spirit of "hack that obviously > shouldn't go upstream until it gets done properly". Yes, it was "quick and dirty". And I do not think it is going upstream in this form...? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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