All of lore.kernel.org
 help / color / mirror / Atom feed
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 June 22
Date: Tue, 22 Jun 2010 20:22:01 +1000	[thread overview]
Message-ID: <20100622202201.638a97f9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTim5sPmqblYvuCsft_Mm7R8ee1NJSwQjw7h6KgqY@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]

On Tue, 22 Jun 2010 09:53:51 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Tue, Jun 22, 2010 at 08:05, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Status of my local build tests will be at
> > http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> 
> Which hasn't changed since June 18?

Yeah, the build server ran out of inodes.  It should update later
tonight/today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-22 10:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  6:05 linux-next: Tree for June 22 Stephen Rothwell
2010-06-22  7:53 ` Geert Uytterhoeven
2010-06-22 10:22   ` Stephen Rothwell [this message]
2010-06-22 15:30 ` linux-next: Tree for June 22 (staging/spectra) Randy Dunlap
2010-06-22 15:59   ` Randy Dunlap
2010-06-22 20:42     ` Greg KH
2010-06-22 16:03 ` [PATCH -next] block/xd.c: fix brace typo Randy Dunlap
2010-06-22 17:24   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2011-06-22  6:36 linux-next: Tree for June 22 Stephen Rothwell
2009-06-22  8:19 Stephen Rothwell
2009-06-22  8:26 ` Stephen Rothwell
2009-06-22 17:23   ` Thorsten Leemhuis
2009-06-23  1:48     ` 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=20100622202201.638a97f9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.