linux-kernel - Re: [PATCH] rtc: add x86 support for rtc-efi

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090420172045.GA17887@elte.hu>
Date:	Mon, 20 Apr 2009 19:20:45 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Brian Maly <bmaly@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, h.peter.anvin@...el.com,
	linux-kernel@...r.kernel.org, dannf@...com, ying.huang@...el.com
Subject: Re: [PATCH] rtc: add x86 support for rtc-efi


* Brian Maly <bmaly@...hat.com> wrote:

>> Hm, it would be nice to first unify the relevant bits of 
>> arch/x86/kernel/time_{32|64}.c into arch/x86/kernel/time.c, and 
>> then we can apply such patches without duplicative effects.
>
> Ingo,
>
> Are you OK with consolidating this into arch/x86/kernel/rtc.c as 
> Huang Ying had suggested? This seems like the most logical place 
> for the rtc-efi init to happen, but your suggestion to consolidate 
> this into arch/x86/kernel.time.c may have advantages that I am not 
> aware of.  Anyway, I would appreciate any insight/opinions on this 
> if you have any.  Thanks.

Yes, that indeed sounds like an even better place for it.

Thanks,

	Ingo
--
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/