public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Lutomirski <luto@amacapital•net>
Cc: Paul Gortmaker <paul.gortmaker@windriver•com>,
	"H. Peter Anvin" <hpa@zytor•com>,
	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>
Subject: Re: [PATCH 0/2] x86,vdso: vdso build fixes and improvements
Date: Fri, 30 May 2014 15:42:29 +1000	[thread overview]
Message-ID: <20140530154229.46d76630@canb.auug.org.au> (raw)
In-Reply-To: <CALCETrVSG7-=Q3sG87YTzDYOLXzEbkvW9Ws=HeJ5cAUGxQhdJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

Hi Andy,

On Thu, 29 May 2014 15:49:52 -0700 Andy Lutomirski <luto@amacapital•net> wrote:
>
> On Thu, May 29, 2014 at 3:41 PM, Paul Gortmaker
> <paul.gortmaker@windriver•com> wrote:
> > On 14-05-29 05:57 PM, Andy Lutomirski wrote:
> >> 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.
> >
> > Since the x86 builds are unconditionally failing as-is now in
> > linux-next, perhaps Stephen [Cc'd] can layer these on the top of
> > the tree he'll be making within the next couple of hours to give
> > them a big-endian test.

I added them just after the merge of the tip tree today and will keep
them there until they (or somo other solution) turn up some other way.

> Stephen, if you do this, could you also send me some of the build outputs:
> 
> arch/x86/vdso/*.so.dbg
> arch/x86/vdso/*-image-*.c
> 
> I'd like to verify that the output is correct.  It would be
> unfortunate if the cross-built kernel had some subtle error.

OK, I will send them in a separate email.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-30  5:42 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           ` [PATCH 0/2] x86,vdso: vdso build fixes and improvements Andy Lutomirski
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 [this message]
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=20140530154229.46d76630@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --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=luto@amacapital$(echo .)net \
    --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