From: Stefani Seibold <stefani@seibold.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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,
Martin.Runge@rohde-schwarz.com, Andreas.Brief@rohde-schwarz.com
Subject: Re: Add 32 bit VDSO time function support
Date: Tue, 04 Mar 2014 17:18:36 +0100 [thread overview]
Message-ID: <1393949916.977.5.camel@wall-e.seibold.net> (raw)
In-Reply-To: <f7c4e803-8b7e-45b7-8f6a-53d3dc561a48@email.android.com>
Am Montag, den 03.03.2014, 23:20 -0800 schrieb H. Peter Anvin:
> Pretty much... contact the glibc maintainers. However, with glibc being a GNU project you will have to sign a copyright transfer.
>
> On March 3, 2014 11:02:08 PM PST, Stefani Seibold <stefani@seibold.net> wrote:
> >Hi,
> >
> >i want ask if there is a change to bring the patch back to tip?
> >
> >As requested the glibc patch is now available at
> >
> >http://seibold.net/glibc.patch
> >
> >Any idea how to bring this patch into glibc? Is the process similar to
> >the kernel?
> >
I got responds from the glibc mailing list:
> Finally GLIBC current policy is to accept kernel internal
> that are *already* implemented in Linux kernel, so the vDSO support do x86 32 bit kernel
> should be either published in a kernel release on pushed in a stable kernel tree (usually
> vanilla one).
So till the 32 bit VDSO time functions are not in the vanilla kernel
tree, there is no way to get in the patch into glibc.
- Stefani
prev parent reply other threads:[~2014-03-04 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 7:02 Add 32 bit VDSO time function support Stefani Seibold
2014-03-04 7:20 ` H. Peter Anvin
2014-03-04 16:18 ` Stefani Seibold [this message]
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=1393949916.977.5.camel@wall-e.seibold.net \
--to=stefani@seibold.net \
--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=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox