linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: linux-next: Tree for August 12
Date: Wed, 13 Aug 2008 09:18:58 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0808130917300.28400@anakin> (raw)
In-Reply-To: <20080812185345.d7496513.sfr@canb.auug.org.au>

On Tue, 12 Aug 2008, Stephen Rothwell wrote:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.

It seems the global overview of the various trees at
http://kisskb.ellerman.id.au/kisskb/matrix/ is no longer updated?
The per-tree overviews are still up-to-date.

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

  parent reply	other threads:[~2008-08-13  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  8:53 linux-next: Tree for August 12 Stephen Rothwell
2008-08-12 17:32 ` [BUG] linux-next: Tree for August 11/12 - powerpc - oops at __kmalloc_node_track_caller () Kamalesh Babulal
2008-08-12 18:28   ` Christoph Lameter
2008-08-16 23:10     ` Kamalesh Babulal
2008-08-18 13:56       ` Christoph Lameter
2008-08-13  7:18 ` Geert Uytterhoeven [this message]
2008-08-13  7:38   ` linux-next: Tree for August 12 Stephen Rothwell
2008-08-13 15:21     ` Michael Ellerman
2009-08-12  6:59 Stephen Rothwell
2009-08-12 14:37 ` Sachin Sant
2010-08-12  6:04 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.0808130917300.28400@anakin \
    --to=geert@linux-m68k.org \
    --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).