[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVSG7-=Q3sG87YTzDYOLXzEbkvW9Ws=HeJ5cAUGxQhdJA@mail.gmail.com>
Date: Thu, 29 May 2014 15:49:52 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Josh Boyer <jwboyer@...oraproject.org>,
Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH 0/2] x86,vdso: vdso build fixes and improvements
On Thu, May 29, 2014 at 3:41 PM, Paul Gortmaker
<paul.gortmaker@...driver.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.
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.
Thanks,
Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists