| 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: <20080521.095624.25479790.nemoto@toshiba-tops.co.jp> Date: Wed, 21 May 2008 09:56:24 +0900 (JST) From: Atsushi Nemoto <anemo@....ocn.ne.jp> To: macro@...ux-mips.org Cc: a.zummo@...ertech.it, hvr@....org, akpm@...ux-foundation.org, rtc-linux@...glegroups.com, linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] RTC: M41T80: Century Bit support On Tue, 20 May 2008 20:51:56 +0100 (BST), "Maciej W. Rozycki" <macro@...ux-mips.org> wrote: > Well, Andrew has applied this patch to the -mm tree now and after a bit > of thinking I have made up my mind and decided we should keep the patch. > This is an I2C device which means it will always only be explicitly > requested by platform code. This is an opportunity for the platform to > express the will and the way to use the century bit. > > I'll cook-up a follow-on patch as soon as the SWARM bits propagate to > upstream, to add a set of flags that will let platforms specify the > desired way the century bit is meant to be handled and which this driver > will honour. Please feel free to keep the interpretation within your pet > board intact -- the flags will be capable to express your needs. OK, it would be the best way to handle the century bit. I'll test your patch (if my board is still alive at the time ;-)) --- Atsushi Nemoto -- 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