From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Frederic Weisbecker <fweisbec@gmail•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for April 30
Date: Mon, 3 May 2010 17:29:28 +1000 [thread overview]
Message-ID: <20100503172928.5fd91af6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100430192748.GC5357@nowhere>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Hi Frederic,
On Fri, 30 Apr 2010 21:27:50 +0200 Frederic Weisbecker <fweisbec@gmail•com> wrote:
>
> On Fri, Apr 30, 2010 at 04:35:38PM +1000, Stephen Rothwell wrote:
> >
> > Changes since 20100429:
> >
> > 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?
That would be because I fetched your tree on Friday before your fixes were
publically available. It is all ok today, thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-03 7:29 UTC|newest]
Thread overview: 10+ 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 ` linux-next: Tree for April 30 Frederic Weisbecker
2010-05-03 7:29 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 7:29 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=20100503172928.5fd91af6.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=fweisbec@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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