From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alan Cox <alan@lxorguk•ukuu.org.uk>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Subject: Re: linux-next: Tree for November 25
Date: Fri, 26 Nov 2010 09:31:07 +1100 [thread overview]
Message-ID: <20101126093107.e54847da.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101125132518.1c7ebed1@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi Alan,
On Thu, 25 Nov 2010 13:25:18 +0000 Alan Cox <alan@lxorguk•ukuu.org.uk> wrote:
>
> Umm where did all the x86 changes go ?
>
> I was going to look at SEP and fixing it but I can't even build a base
> test tree from -next because all the x86 work seems to be missing from
> the tree from 23rd onwards.
You need to ask the x86, staging and tip maintainers ... There was a
build failure in tip tree on Nov 23 after which the tip tree was rebuilt
without some of its branches. Also, there is a boot failure caused by
the sep driver (which I see one of your patches should fix).
I did not remove any of the code.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-11-25 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 5:49 linux-next: Tree for November 25 Stephen Rothwell
2010-11-25 13:25 ` Alan Cox
2010-11-25 22:31 ` Stephen Rothwell [this message]
2010-11-25 14:24 ` Zimny Lech
2010-11-26 2:45 ` linux-next: Tree for November 25 (snd/soc/codecs) Randy Dunlap
2010-11-26 11:21 ` Mark Brown
2010-11-26 16:27 ` Randy Dunlap
2010-11-26 16:30 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-11-25 12:53 linux-next: Tree for November 25 Stephen Rothwell
2008-11-25 10:37 Stephen Rothwell
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=20101126093107.e54847da.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--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