[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53222C78.3020408@zytor.com>
Date: Thu, 13 Mar 2014 15:08:56 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Stefani Seibold <stefani@...bold.net>
CC: Andy Lutomirski <luto@...capital.net>,
Greg KH <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, X86 ML <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Andi Kleen <ak@...ux.intel.com>,
Andrea Arcangeli <aarcange@...hat.com>,
John Stultz <john.stultz@...aro.org>,
Pavel Emelyanov <xemul@...allels.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
andriy.shevchenko@...ux.intel.com,
Martin Runge <Martin.Runge@...de-schwarz.com>,
Andreas Brief <Andreas.Brief@...de-schwarz.com>
Subject: Re: [PATCH 0/3] Improve 32 bit vDSO time
On 03/13/2014 01:11 AM, Stefani Seibold wrote:
> Am Mittwoch, den 12.03.2014, 20:48 -0700 schrieb H. Peter Anvin:
>> On 03/12/2014 04:11 PM, stefani@...bold.net wrote:
>>>
>>> I will do this when your patch is pulled into tip. For now we have the
>>> choice, but i preferer our solution removing the compat vdso.
>>>
>>
>> Sorry, that didn't parse from me.
>
> I thought it is a good idea to wait until the "remove compat vdso
> support" is settled and pulled into tip.
>
> If there is no objections against this patch i am happy to do the
> job ;-)
>
> BTW: Thanks to Andy for doing this job to git rid off this ugly compat
> vDSO layer.
>
>> Also, if you state a preference, could you please motivate it?
>
> For the next three days i am very busy with a important project, so i
> will rebase the vdso 32 bit time patch on Monday or Tuesday.
>
So when I get the updated patch from Andy I will pull it into tip,
resetting the x86/vdso branch. I'll then expect an upgraded and
simplified patchset from you to put on top.
Sounds like a plan.
-hpa
--
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