From: "H. Peter Anvin" <hpa@zytor.com>
To: stefani@seibold.net, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, ak@linux.intel.com, aarcange@redhat.com,
john.stultz@linaro.org, luto@amacapital.net, xemul@parallels.com,
gorcunov@openvz.org, andriy.shevchenko@linux.intel.com
Cc: Martin.Runge@rohde-schwarz.com, Andreas.Brief@rohde-schwarz.com
Subject: Re: [PATCH v15 0/10] Add 32 bit VDSO time function support
Date: Thu, 13 Feb 2014 22:47:50 -0800 [thread overview]
Message-ID: <52FDBC16.10101@zytor.com> (raw)
In-Reply-To: <1392237483-6421-1-git-send-email-stefani@seibold.net>
Hi,
I tried this patchset, but it fails to compile on i386 "make allyesconfig".
-hpa
next prev parent reply other threads:[~2014-02-14 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 20:37 [PATCH v15 0/10] Add 32 bit VDSO time function support stefani
2014-02-12 20:37 ` [PATCH v15 01/10] Make vsyscall_gtod_data handling x86 generic stefani
2014-02-12 20:37 ` [PATCH v15 02/10] Add new func _install_special_mapping() to mmap.c stefani
2014-02-12 20:37 ` [PATCH v15 03/10] revamp vclock_gettime.c stefani
2014-02-12 20:37 ` [PATCH v15 04/10] vclock_gettime.c __vdso_clock_gettime cleanup stefani
2014-02-12 20:37 ` [PATCH v15 05/10] replace VVAR(vsyscall_gtod_data) by gtod macro stefani
2014-02-12 20:37 ` [PATCH v15 06/10] cleanup __vdso_gettimeofday stefani
2014-02-12 20:38 ` [PATCH v15 07/10] introduce VVAR marco for vdso32 stefani
2014-02-12 20:38 ` [PATCH v15 08/10] Add 32 bit VDSO time support for 32 bit kernel stefani
2014-02-12 20:38 ` [PATCH v15 09/10] Add 32 bit VDSO time support for 64 " stefani
2014-02-14 6:47 ` H. Peter Anvin [this message]
2014-02-14 7:48 ` [PATCH v15 0/10] Add 32 bit VDSO time function support Stefani Seibold
2014-02-14 7:50 ` H. Peter Anvin
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=52FDBC16.10101@zytor.com \
--to=hpa@zytor.com \
--cc=Andreas.Brief@rohde-schwarz.com \
--cc=Martin.Runge@rohde-schwarz.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gorcunov@openvz.org \
--cc=gregkh@linuxfoundation.org \
--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.