From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: linux-next: build failure after merge of the arm tree
Date: Sun, 19 Jan 2020 22:02:30 +0000 [thread overview]
Message-ID: <20200119220230.GX25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200120082447.7fea4d55@canb.auug.org.au>
Hi Stephen,
Patch dropped.
I think this needs to wait until it's been properly tested before I
apply the next version.
On Mon, Jan 20, 2020 at 08:24:47AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
>
> Caused by commit
>
> e3a0e1427dcb ("ARM: 8953/1: decompressor: simplify libfdt builds")
>
> My arm builds are ppc64le hosted cross compiles using Debian's cross
> gcc package.
>
> I have reverted that commit for today.
> --
> Cheers,
> Stephen Rothwell
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2020-01-19 22:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 21:24 linux-next: build failure after merge of the arm tree Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 23:46 Stephen Rothwell
2024-11-13 0:25 ` Stephen Rothwell
2024-08-20 23:36 Stephen Rothwell
2024-08-21 3:27 ` liuyuntao (F)
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2021-10-25 23:25 Stephen Rothwell
2017-04-20 22:40 Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 7:58 ` Mason
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-22 8:41 ` Mason
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-04-24 4:20 ` Vinod Koul
2017-06-14 19:23 ` Mason
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2017-04-21 11:27 ` Mason
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
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=20200119220230.GX25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@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 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.