From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: linux-next: Tree for April 24
Date: Thu, 24 Apr 2008 13:12:16 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804241311330.7107@anakin> (raw)
In-Reply-To: <20080424193023.862cacd7.sfr@canb.auug.org.au>
On Thu, 24 Apr 2008, Stephen Rothwell wrote:
> On Thu, 24 Apr 2008 09:45:57 +0200 (CEST) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > For m68k, I've added multi_defconfig, to build a kernel for all supported m68k
> > platforms, excluding Sun 3 (Sun 3 kernels are incompatible with all other m68k
> > platforms).
> >
> > Hence if you would build multi_defconfig and sun3_defconfig, you cover all of
> > our platforms and drivers.
>
> Done. Thanks.
BTW, the results of today all seem to are unaccessible?
E.g. http://kisskb.ellerman.id.au/kisskb/buildresult/25192/
Forbidden
You don't have permission to access /kisskb/buildresult/25195/ on this
server.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-04-24 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 7:36 Stephen Rothwell
2008-04-24 7:45 ` Geert Uytterhoeven
2008-04-24 9:30 ` Stephen Rothwell
2008-04-24 11:12 ` Geert Uytterhoeven [this message]
2008-04-25 7:20 ` Stephen Rothwell
2008-04-25 13:32 ` Michael Ellerman
2008-04-25 14:18 ` Sebastian Siewior
2008-04-24 19:40 ` Geert Uytterhoeven
2008-04-24 19:44 ` Christoph Hellwig
2009-04-24 5:04 Stephen Rothwell
2009-04-26 13:20 ` Benny Halevy
2009-04-27 4:21 ` 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=Pine.LNX.4.64.0804241311330.7107@anakin \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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
all inboxes | Powered by JetHome®