From: Alex Elder <aelder@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 27
Date: Tue, 27 Jul 2010 13:35:43 -0500 [thread overview]
Message-ID: <1280255743.2002.184.camel@doink> (raw)
In-Reply-To: <20100727160708.722c39c1.sfr@canb.auug.org.au>
On Tue, 2010-07-27 at 16:07 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100726:
>
> The arm tree lost its conflict.
>
> The microblaze tree lost its conflict.
>
> The mips tree gained a build failure so I used the version from
> next-20100726.
>
> The xfs tree still has its build failure so I used the version from
> next-20100723.
The XFS master branch has been updated. It includes
a fix for the problem caused by this commit:
0fd7275cc42ab734eaa1a2c747e65479bd1e42af
...which was is the cause of this linux-next build failure.
The branch has also been re-based to 2.6.35-rc6.
-Alex
next prev parent reply other threads:[~2010-07-27 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 6:07 linux-next: Tree for July 27 Stephen Rothwell
2010-07-27 7:24 ` Jaswinder Singh Rajput
2010-07-27 7:28 ` Stephen Rothwell
2010-07-27 18:35 ` Alex Elder [this message]
2010-07-28 1:24 ` Stephen Rothwell
2010-07-27 18:38 ` linux-next: Tree for July 27 (xen) Randy Dunlap
2010-07-28 13:11 ` Stefano Stabellini
2010-07-28 14:48 ` Jeremy Fitzhardinge
2010-07-28 15:06 ` Stefano Stabellini
2010-07-28 15:47 ` Randy Dunlap
2010-07-27 19:21 ` [PATCH -next] staging/line6: needs to select SND_PCM Randy Dunlap
2010-07-27 19:21 ` Randy Dunlap
2010-07-28 13:59 ` Takashi Iwai
2010-07-28 15:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-07-27 4:21 linux-next: Tree for July 27 Stephen Rothwell
2011-07-27 4:11 Stephen Rothwell
2009-07-27 8:05 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=1280255743.2002.184.camel@doink \
--to=aelder@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.