From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 7
Date: Mon, 7 Jan 2019 08:35:36 +0100 [thread overview]
Message-ID: <CAMuHMdUCKaADLBrv0KLXSYHe8bR3ws7mhYr+1SkFYW15kDGo9Q@mail.gmail.com> (raw)
In-Reply-To: <20190107150609.0510def3@canb.auug.org.au>
Hi Stephen, Michael,
Happy NY! Looking forward to lots of linux-next releases and build
logs in 2019 ;-)
On Mon, Jan 7, 2019 at 5:08 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.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /kisskb/.
Reason: Error reading from remote server
Apache/2.4.37 (Debian) Server at kisskb.ellerman.id.au Port 80
Oops...
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:[~2019-01-07 7:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 4:06 linux-next: Tree for Jan 7 Stephen Rothwell
2019-01-07 7:35 ` Geert Uytterhoeven [this message]
2019-01-07 11:49 ` Michael Ellerman
2019-01-07 13:56 ` Michael Ellerman
2019-01-08 2:28 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2025-01-07 5:53 Stephen Rothwell
2022-01-07 15:43 Stephen Rothwell
2021-01-07 3:01 Stephen Rothwell
2020-01-07 6:03 Stephen Rothwell
2016-01-07 10:21 Stephen Rothwell
2015-01-07 4:16 Stephen Rothwell
2015-01-07 7:34 ` Sedat Dilek
2015-01-07 14:26 ` Guenter Roeck
2015-01-07 16:33 ` Paul E. McKenney
2015-01-07 17:30 ` Guenter Roeck
2015-01-07 18:09 ` Paul E. McKenney
2015-01-07 19:18 ` Guenter Roeck
2015-01-07 20:00 ` Christian Borntraeger
2015-01-07 20:33 ` Guenter Roeck
2014-01-07 6:38 Stephen Rothwell
2013-01-07 3:26 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=CAMuHMdUCKaADLBrv0KLXSYHe8bR3ws7mhYr+1SkFYW15kDGo9Q@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@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).