linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
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 26
Date: Tue, 26 Jul 2011 11:34:27 +0200	[thread overview]
Message-ID: <4E2E8A23.6000601@monstr.eu> (raw)
In-Reply-To: <20110726155744.5c1bee67177bd94211ed8c2b@canb.auug.org.au>

Hi Stephen,

Stephen Rothwell wrote:
> Hi all,
> 
> The powerpc allyesconfig build (at least) still fails today.
> 
> Changes since 20110725:
> 
> Undropped tree: iscsi-target
> 
> Linus' tree lost its build failure but gained another for which I applied
> a patch (supplied by Linus).
> 
> The m68knommu tree lost its conflicts.
> 
> The microblaze tree gained a conflict agains Linus' tree.

Have fixed this problem by reverting one pci patch. Will wait one more day 
before I send pull request.

Thanks,
Micha


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2011-07-26  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  5:57 linux-next: Tree for July 26 Stephen Rothwell
2011-07-26  9:34 ` Michal Simek [this message]
2011-07-26 21:30 ` linux-next: Tree for July 26 (gpu vs. staging/gma500) Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2012-07-26  5:04 linux-next: Tree for July 26 Stephen Rothwell
2010-07-26  5:48 Stephen Rothwell
2010-07-26  8:53 ` Michal Simek
2010-07-26  9:19   ` 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=4E2E8A23.6000601@monstr.eu \
    --to=monstr@monstr.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).