From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 19
Date: Wed, 23 Dec 2009 18:52:04 +1100 [thread overview]
Message-ID: <20091223185204.93e59989.sfr@canb.auug.org.au> (raw)
In-Reply-To: <10f740e80912190042o474b6188ga32fcc4ff0846531@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi Geert,
On Sat, 19 Dec 2009 09:42:19 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Sat, Dec 19, 2009 at 01:04, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Well, I decided I had time for one more so it will be based in -rc1).
>
> Hurray!
:-)
> But http://kisskb.ellerman.id.au/kisskb/buildresult/1852835/ shows
> linux-next/m68k-allmodconfig fails
> in security/keys/keyctl.c, while this got fixed in 2.6.33-rc1?? It
> compiled fine in linus/m68k-allmodconfig,
> as expected
That build was of next-20091218 ... the build of next-20091219
(http://kisskb.ellerman.id.au/kisskb/buildresult/1853405/) failed
differently :-(
--
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:[~2009-12-23 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 0:04 Stephen Rothwell
2009-12-19 3:10 ` linux-next: Tree for December 19 (staging/dt3155) Randy Dunlap
2009-12-19 4:47 ` Greg KH
2010-02-11 16:44 ` Randy Dunlap
2010-02-11 16:54 ` Greg KH
2009-12-19 3:18 ` linux-next: Tree for December 19 (media/mantis) Randy Dunlap
2009-12-19 17:11 ` Manu Abraham
2009-12-19 18:30 ` Randy Dunlap
2009-12-19 8:42 ` linux-next: Tree for December 19 Geert Uytterhoeven
2009-12-23 7:52 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-19 12:57 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=20091223185204.93e59989.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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
all inboxes | Powered by JetHome®