From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linux-next@vger•kernel.org, linus.walleij@linaro•org
Subject: Re: linux-next: Tree for Jan 24
Date: Tue, 28 Jan 2014 10:28:33 +1100 [thread overview]
Message-ID: <20140128102833.188b0ecb3d0d627b3d31ea30@canb.auug.org.au> (raw)
In-Reply-To: <20140127174756.GA21205@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Hi Paul,
On Mon, 27 Jan 2014 12:47:57 -0500 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
>
> While looking over some of the other fails, I noticed arm
> shark_defconfig build failure:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/10510182/
>
> We can simply drop this build entirely, due to this commit:
>
> commit 136dfa5edae3207422a8b93347eb79e92e07cdfa
> Author: Linus Walleij <linus.walleij@linaro•org>
> Date: Tue Sep 3 11:32:24 2013 +0200
>
> ARM: delete mach-shark
>
> The last passing build was Sept 26, so apologies if this has been
> reported since then.
Thanks for pointing it out - I have removed the build.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-27 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 4:40 linux-next: Tree for Jan 24 Stephen Rothwell
2014-01-27 17:47 ` Paul Gortmaker
2014-01-27 23:28 ` Stephen Rothwell [this message]
2014-01-27 17:58 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2025-01-24 4:51 Stephen Rothwell
2024-01-24 4:36 Stephen Rothwell
2023-01-24 3:40 Stephen Rothwell
2022-01-24 0:35 Stephen Rothwell
2020-01-24 6:33 Stephen Rothwell
2019-01-24 6:29 Stephen Rothwell
2017-01-24 5:46 Stephen Rothwell
2013-01-24 6:13 Stephen Rothwell
2012-01-24 5:30 Stephen Rothwell
2012-01-24 23:18 ` Rafael J. Wysocki
2012-01-24 23:20 ` 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=20140128102833.188b0ecb3d0d627b3d31ea30@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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