| 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: Mon, 08 Sep 2008 14:35:04 -0700 (PDT) From: David Miller <davem@...emloft.net> To: david-b@...bell.net Cc: James.Bottomley@...senpartnership.com, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC From: David Brownell <david-b@...bell.net> Date: Mon, 8 Sep 2008 14:29:57 -0700 > On Monday 08 September 2008, James Bottomley wrote: > > All the PDC real time clock calls can do are read and set, nothing else, > > so it's idealy suited to the GEN_RTC infrastructure ... what's the > > benefit in moving it to RTC_CLASS? > > The same benefit always found in sharing infrastructure. Lots > of little differences/bugs go away. Infrastructure improvements > and bugfixes get leveraged. Dead and crufticious code can vanish. > And so forth. I absolutely and positively agree with David here. I just last week converted all of both sparc ports to the generic RTC layer and what a huge burdon has been moved off of my shoulders. The RTC layer is very nice and it even allows writing drivers for very simplistic RTC devices (even ones that cannot be written) with ease. I had two such cases to handle on sparc64. -- 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