All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.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 August 5
Date: Wed, 05 Aug 2009 11:11:20 +0300	[thread overview]
Message-ID: <4A793EA8.50306@panasas.com> (raw)
In-Reply-To: <20090805172337.b0688db1.sfr@canb.auug.org.au>

On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20090804:
> 
> This tree fails to build for powerpc allyesconfig (final link problem).
> 

Above is reported for a long time. Is it related to this:
http://www.spinics.net/lists/kernel/msg921978.html

> The mfd tree gained a conflict against the input tree.
> 
> The drm tree gained a conflict against Linus' tree.
> 
> The edac-amd tree gained a conflict against Linus' tree.
> 
> ----------------------------------------------------------------------------
> 
<snip>

  reply	other threads:[~2009-08-05  8:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  7:23 linux-next: Tree for August 5 Stephen Rothwell
2009-08-05  8:11 ` Boaz Harrosh [this message]
2009-08-05 10:13   ` Stephen Rothwell
2009-08-05 10:13     ` Stephen Rothwell
2009-08-05 10:13     ` Stephen Rothwell
2009-08-05 13:28     ` Boaz Harrosh
2009-08-05 13:28       ` Boaz Harrosh
2009-08-05 16:26 ` [PATCH -next] isdn: fix netjet build errors Randy Dunlap
2009-08-05 19:03   ` David Miller
2009-08-06  5:05     ` Karsten Keil
2009-08-06 20:10       ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2010-08-05  4:04 linux-next: Tree for August 5 Stephen Rothwell
2008-08-05  7:59 Stephen Rothwell
2008-08-05 15:49 ` Stefan Richter
2008-08-05 15:55   ` David Woodhouse

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=4A793EA8.50306@panasas.com \
    --to=bharrosh@panasas.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.