linux-next.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>,
	Michael Ellerman <michael@ellerman.id.au>
Cc: Linux-Next <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 4
Date: Tue, 4 Nov 2014 22:56:40 +0100	[thread overview]
Message-ID: <CAMuHMdVfTK4xEu33YMay9naTThvhRLdCpVCQLHW1FSW643mSAw@mail.gmail.com> (raw)
In-Reply-To: <20141104173624.67dd3286@canb.auug.org.au>

Hi Stephen, Michael,

On Tue, Nov 4, 2014 at 7:36 AM, 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
> advice about cross compilers/configs that work, we are always open to add
> more builds.

Looks like the build results got stuck on Nov 3? There are also no
results for v3.18-rc3 yet.

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:[~2014-11-04 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  6:36 linux-next: Tree for Nov 4 Stephen Rothwell
2014-11-04 20:57 ` Guenter Roeck
2014-11-04 21:56 ` Geert Uytterhoeven [this message]
2014-11-05  2:07   ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04  5:21 Stephen Rothwell
2021-11-04  4:02 Stephen Rothwell
2020-11-04  6:01 Stephen Rothwell
2015-11-04  6:38 Stephen Rothwell
2013-11-04  6:59 Stephen Rothwell
2011-11-04  5:25 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=CAMuHMdVfTK4xEu33YMay9naTThvhRLdCpVCQLHW1FSW643mSAw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --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).