public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital•net>
To: Paul Gortmaker <paul.gortmaker@windriver•com>,
	"H. Peter Anvin" <hpa@zytor•com>
Cc: Josh Boyer <jwboyer@fedoraproject•org>,
	Ingo Molnar <mingo@kernel•org>,
	LKML <linux-kernel@vger•kernel.org>,
	"tglx@linutronix•de" <tglx@linutronix•de>,
	"linux-tip-commits@vger•kernel.org"
	<linux-tip-commits@vger•kernel.org>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
	Andy Lutomirski <luto@amacapital•net>
Subject: [PATCH 0/2] x86,vdso: vdso build fixes and improvements
Date: Thu, 29 May 2014 14:57:16 -0700	[thread overview]
Message-ID: <cover.1401400316.git.luto@amacapital.net> (raw)
In-Reply-To: <CALCETrXef77JLoEp5hCXSdMAk7usWsL-sUG6NrcgLgrz3krfag@mail.gmail.com>

Patch 1 causes make;make to behave similarly to make if vdso2c fails.
Patch 2 hopefully fixes x86 crossbuilds on big-endian machines.  I don't
have a big-endian machine to test on, though.

Andy Lutomirski (2):
  x86,vdso: When vdso2c fails, unlink the output
  x86,vdso: Fix cross-compilation from big-endian architectures

 arch/x86/vdso/vdso2c.c | 35 ++++++++++++++++++-------
 arch/x86/vdso/vdso2c.h | 69 ++++++++++++++++++++++++++------------------------
 2 files changed, 62 insertions(+), 42 deletions(-)

-- 
1.9.3

  reply	other threads:[~2014-05-29 21:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2c4fcf45524162a34d87fdda1eb046b2a5cecee7.1399317206.git.luto@amacapital.net>
     [not found] ` <tip-6f121e548f83674ab4920a4e60afb58d4f61b829@git.kernel.org>
2014-05-29 19:17   ` [tip:x86/vdso] x86, vdso: Reimplement vdso.so preparation in build-time C Paul Gortmaker
2014-05-29 19:32     ` Andy Lutomirski
2014-05-29 19:43       ` H. Peter Anvin
2014-05-29 19:46         ` Andy Lutomirski
2014-05-29 21:57           ` Andy Lutomirski [this message]
2014-05-29 21:57             ` [PATCH 1/2] x86,vdso: When vdso2c fails, unlink the output Andy Lutomirski
2014-05-29 21:57             ` [PATCH 2/2] x86,vdso: Fix cross-compilation from big-endian architectures Andy Lutomirski
2014-05-29 22:41             ` [PATCH 0/2] x86,vdso: vdso build fixes and improvements Paul Gortmaker
2014-05-29 22:49               ` Andy Lutomirski
2014-05-30  5:42                 ` Stephen Rothwell
2014-05-30 15:40                   ` Andy Lutomirski
2014-05-30 15:48           ` [PATCH v2 " Andy Lutomirski
2014-05-30 15:48             ` [PATCH v2 1/2] x86,vdso: When vdso2c fails, unlink the output Andy Lutomirski
2014-05-30 15:48             ` [PATCH v2 2/2] x86,vdso: Fix cross-compilation from big-endian architectures Andy Lutomirski
2014-05-30 20:02               ` H. Peter Anvin
2014-05-30 20:09                 ` Andy Lutomirski
2014-05-30 20:21                   ` H. Peter Anvin
2014-05-30 20:34                     ` Andy Lutomirski
2014-05-31  0:14                       ` H. Peter Anvin
2014-05-29 19:43       ` [tip:x86/vdso] x86, vdso: Reimplement vdso.so preparation in build-time C Josh Boyer

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=cover.1401400316.git.luto@amacapital.net \
    --to=luto@amacapital$(echo .)net \
    --cc=hpa@zytor$(echo .)com \
    --cc=jwboyer@fedoraproject$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-tip-commits@vger$(echo .)kernel.org \
    --cc=mingo@kernel$(echo .)org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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