| 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: <20080521153223.e989cb88.akpm@linux-foundation.org> Date: Wed, 21 May 2008 15:32:23 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Stas Sergeev <stsp@...et.ru> Cc: linux-kernel@...r.kernel.org, dbrownell@...rs.sourceforge.net, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, stable@...nel.org Subject: Re: [patch] provide rtc_cmos platform device On Tue, 20 May 2008 22:25:56 +0400 Stas Sergeev <stsp@...et.ru> wrote: > Hello. > > Recently (around 2.6.25) I've noticed > that RTC no longer works for me. So it's a regression. > It turned out this is because I use > pnpacpi=off kernel option to work > around the parport_pc bugs. > I always did so, but RTC used to work > fine in the past, and now it have > regressed. Albeit a fairly obscure one. I tagged the patch for backporting, let those guys decide ;) > The attached patch fixes the problem > by creating the platform device for > the RTC when PNP is disabled. > This may also help running the > PNP-enabled kernel on an older PCs. > > Signed-off-by: Stas Sergeev <stsp@...et.ru> I suppose that on this basis: arch/x86/kernel/rtc.c | 31 +++++++++++++++++++++++++++++++ drivers/rtc/rtc-cmos.c | 26 +++++++++----------------- include/asm-x86/rtc.h | 4 ++++ it should be considered an x86 patch. I shall treat it as such. Thanks. -- 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