| 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: Fri, 28 Jun 2013 11:01:58 -0400 From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> To: Thomas Gleixner <tglx@...utronix.de> Cc: David Vrabel <david.vrabel@...rix.com>, xen-devel@...ts.xen.org, LKML <linux-kernel@...r.kernel.org>, John Stultz <john.stultz@...aro.org> Subject: Re: [PATCHv6 0/5] xen: maintain an accurate persistent clock in more cases On Fri, Jun 28, 2013 at 03:14:42PM +0200, Thomas Gleixner wrote: > On Thu, 27 Jun 2013, David Vrabel wrote: > > These series fixes the above limitations and depends on "x86: increase > > precision of x86_platform.get/set_wallclock()" which was previously > > posted. > > So I'd like to merge that in the following way: > > I pick up patches 1-3 and stick them into tip timers/for-xen and merge > that branch into timers/core. When picking up 1/6, I'll drop the xen > part of that, so timers/core will not hold any xen specific bits. > > Then the xen folks can pull timers/for-xen and apply the xen specific > stuff on top. Wouldn't it be easier for you to pick the "xen part of that" as well? I am OK with you doing that and it all going through your tree. But if it is easier for you to do the way you said - I can do that too. Just tell me when to pull timers/for-xen > > Thanks, > > tglx > > -- 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