From: Andi Kleen <ak@linux.intel.com>
To: Stefani Seibold <stefani@seibold.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, aarcange@redhat.com, john.stultz@linaro.org,
luto@amacapital.net, xemul@parallels.com, gorcunov@openvz.org,
andriy.shevchenko@linux.intel.com,
Martin.Runge@rohde-schwarz.com, Andreas.Brief@rohde-schwarz.com
Subject: Re: [PATCH v16 0/10] Add 32 bit VDSO time function support
Date: Fri, 14 Feb 2014 12:17:54 -0800 [thread overview]
Message-ID: <20140214201754.GT12219@tassilo.jf.intel.com> (raw)
In-Reply-To: <1392367964-32118-1-git-send-email-stefani@seibold.net>
This version looks good to me from a quick read.
-Andi
next prev parent reply other threads:[~2014-02-14 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 8:52 [PATCH v16 0/10] Add 32 bit VDSO time function support Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 01/10] Make vsyscall_gtod_data handling x86 generic Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 02/10] Add new func _install_special_mapping() to mmap.c Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 03/10] revamp vclock_gettime.c Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 04/10] vclock_gettime.c __vdso_clock_gettime cleanup Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 05/10] replace VVAR(vsyscall_gtod_data) by gtod macro Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 06/10] cleanup __vdso_gettimeofday Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 07/10] introduce VVAR marco for vdso32 Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 08/10] Add 32 bit VDSO time support for 32 bit kernel Stefani Seibold
2014-02-14 8:52 ` [PATCH v16 09/10] Add 32 bit VDSO time support for 64 " Stefani Seibold
2014-02-14 20:17 ` Andi Kleen [this message]
2014-02-14 22:32 ` [PATCH v16 0/10] Add 32 bit VDSO time function support H. Peter Anvin
2014-02-15 14:33 ` Stefani Seibold
2014-02-15 18:42 ` H. Peter Anvin
2014-02-14 22:40 ` Andy Lutomirski
2014-02-15 2:48 ` Greg KH
2014-02-15 15:05 ` Stefani Seibold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140214201754.GT12219@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=Andreas.Brief@rohde-schwarz.com \
--cc=Martin.Runge@rohde-schwarz.com \
--cc=aarcange@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gorcunov@openvz.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=stefani@seibold.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.