From: Frederic Weisbecker <fweisbec@gmail.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 April 30
Date: Fri, 30 Apr 2010 21:27:50 +0200 [thread overview]
Message-ID: <20100430192748.GC5357@nowhere> (raw)
In-Reply-To: <20100430163538.7253a9e0.sfr@canb.auug.org.au>
On Fri, Apr 30, 2010 at 04:35:38PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100429:
>
> Dropped trees: tmio-mmc (long unresolved conflicts and unable to fetch)
> hwlat (at the maintainer's request)
>
> My fixes tree contains:
> a patch for a pktcdvd build error from Arnd Bergmann
>
> The v4l-dvb tree still has its build failure, so I used the version from
> next-20100409.
>
> The block tree lost a conflict and its build failure but gained another
> conflict against the ext3 tree.
>
> The bk-ioctl tree still has its build failure so I used the version from
> next-20100428.
That looks weird, I fixed all the reported conflicts and build error you
reported. Or may be there are some others left that I missed in allyesconfig?
Thanks.
next prev parent reply other threads:[~2010-04-30 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 6:35 linux-next: Tree for April 30 Stephen Rothwell
2010-04-30 17:50 ` linux-next: Tree for April 30 (CONFIG_SYSFS=n) Randy Dunlap
2010-05-05 16:17 ` Randy Dunlap
2010-05-05 16:24 ` Greg KH
2010-05-05 21:35 ` Eric W. Biederman
2010-05-05 21:54 ` [PATCH] sysfs: Don't use enums in inline function declaration Eric W. Biederman
2010-05-05 22:05 ` Randy Dunlap
2010-04-30 19:27 ` Frederic Weisbecker [this message]
2010-05-03 7:29 ` linux-next: Tree for April 30 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 7:29 Stephen Rothwell
2008-04-30 7:31 Stephen Rothwell
2008-04-30 7:34 ` David Miller
2008-04-30 7:37 ` Stephen Rothwell
2008-04-30 7:52 ` David Miller
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=20100430192748.GC5357@nowhere \
--to=fweisbec@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox