From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Kui Zhang <kuizhang@gmail.com>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] x86,vdso: Hack to keep 64-bit Go programs working
Date: Thu, 12 Jun 2014 18:54:45 -0700 [thread overview]
Message-ID: <539A59E5.2050206@zytor.com> (raw)
In-Reply-To: <CALCETrXttYofO89Y40mYC2xXjZxuJbenAUNY+2w=vT5nr3F7VA@mail.gmail.com>
On 06/12/2014 06:52 PM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 6:49 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 06/12/2014 05:53 PM, Andy Lutomirski wrote:
>>>
>>> This is currently broken for big-endian build hosts. The hack
>>> should also be disabled for x32, but I'm not sure what the right way
>>> to do that is.
>>>
>>
>> This comment is obsolete, no?
>
> Yes, it's obsolete. Whoops.
>
> Want a new patch?
>
Nah. I can edit.
-hpa
next prev parent reply other threads:[~2014-06-13 1:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 0:53 [PATCH v3 0/4] vDSO reference parser updates and Go workaround Andy Lutomirski
2014-06-13 0:53 ` [PATCH v3 1/4] doc,vdso: Rename vdso_test.c to vdso_standalone_test_x86.c Andy Lutomirski
2014-06-13 2:27 ` [tip:x86/vdso] x86/vdso/doc: " tip-bot for Andy Lutomirski
2014-06-13 0:53 ` [PATCH v3 2/4] doc,vdso: Make vDSO examples more portable Andy Lutomirski
2014-06-13 2:27 ` [tip:x86/vdso] x86/vdso/doc: " tip-bot for Andy Lutomirski
2014-06-13 0:53 ` [PATCH v3 3/4] x86,vdso: Add PUT_LE to store little-endian values Andy Lutomirski
2014-06-13 2:28 ` [tip:x86/vdso] x86/vdso: " tip-bot for Andy Lutomirski
2014-06-13 0:53 ` [PATCH v3 4/4] x86,vdso: Hack to keep 64-bit Go programs working Andy Lutomirski
2014-06-13 1:49 ` H. Peter Anvin
2014-06-13 1:52 ` Andy Lutomirski
2014-06-13 1:54 ` H. Peter Anvin [this message]
2014-06-13 2:28 ` [tip:x86/vdso] x86/vdso: " tip-bot for Andy Lutomirski
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=539A59E5.2050206@zytor.com \
--to=hpa@zytor.com \
--cc=kuizhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=x86@kernel.org \
/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.