From: Tamar Christina <Tamar.Christina@arm.com>
To: David Miller <davem@davemloft.net>
Cc: "joseph@codesourcery.com" <joseph@codesourcery.com>,
"schwab@linux-m68k.org" <schwab@linux-m68k.org>,
"carlos@redhat.com" <carlos@redhat.com>,
"fweimer@redhat.com" <fweimer@redhat.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
nd <nd@arm.com>, "Bin Cheng" <Bin.Cheng@arm.com>
Subject: RE: [PATCH v4] Fix -Os related build and test failures.
Date: Tue, 01 Nov 2016 16:15:00 -0000 [thread overview]
Message-ID: <VI1PR0801MB2031D3CA18A8EEF0340AB3A9FFA10@VI1PR0801MB2031.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20161101.120625.1755763054875274977.davem@davemloft.net>
Ah, OK. Hadn't noticed.
Thanks!
> -----Original Message-----
> From: David Miller [mailto:davem@davemloft.net]
> Sent: 01 November 2016 16:06
> To: Tamar Christina
> Cc: joseph@codesourcery.com; schwab@linux-m68k.org;
> carlos@redhat.com; fweimer@redhat.com; libc-alpha@sourceware.org; nd;
> Bin Cheng
> Subject: Re: [PATCH v4] Fix -Os related build and test failures.
>
> From: Tamar Christina <Tamar.Christina@arm.com>
> Date: Tue, 1 Nov 2016 15:58:20 +0000
>
> > This also breaks ARM and AArch64,
> >
> > Would it be worth reverting the commit until this is fixed?
> > It's currently blocking trunk builds.
>
> Mainline has been fixed already.
next prev parent reply other threads:[~2016-11-01 16:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 4:48 [PATCH] Fix -Os related -Werror failures Carlos O'Donell
2016-10-28 6:25 ` Andreas Schwab
2016-10-28 6:32 ` Florian Weimer
2016-10-28 6:44 ` Jeff Law
2016-10-28 8:12 ` Arnd Bergmann
2016-10-28 8:17 ` Andrew Pinski
2016-10-28 13:28 ` Jeff Law
2016-10-28 20:10 ` Paul Eggert
2016-10-29 3:03 ` Jeff Law
2016-10-30 4:25 ` Paul Eggert
2016-10-28 12:09 ` Carlos O'Donell
2016-10-28 12:43 ` Florian Weimer
2016-10-28 13:04 ` Joseph Myers
2016-10-28 13:07 ` Carlos O'Donell
2016-10-28 12:49 ` Joseph Myers
2016-10-28 12:55 ` Florian Weimer
2016-10-28 13:18 ` Carlos O'Donell
2016-10-28 13:58 ` [PATCH v2] Fix -Os related build and test failures Carlos O'Donell
2016-10-28 14:17 ` Joseph Myers
2016-10-29 2:59 ` [PATCH v3] " Carlos O'Donell
2016-10-29 3:26 ` Carlos O'Donell
2016-10-29 17:35 ` Joseph Myers
2016-10-30 3:51 ` [PATCH v4] " Carlos O'Donell
2016-10-31 8:33 ` Andreas Schwab
2016-10-31 9:16 ` Carlos O'Donell
2016-10-31 9:22 ` Florian Weimer
2016-10-31 12:56 ` David Miller
2016-10-31 19:56 ` Carlos O'Donell
2016-11-01 22:59 ` Joseph Myers
2016-11-02 12:52 ` Carlos O'Donell
2016-11-01 9:17 ` Andreas Schwab
2016-11-01 11:13 ` Joseph Myers
2016-11-01 15:58 ` Tamar Christina
2016-11-01 16:06 ` David Miller
2016-11-01 16:15 ` Tamar Christina [this message]
2016-11-02 11:53 ` Carlos O'Donell
2016-11-02 17:03 ` Carlos O'Donell
2016-11-02 13:22 ` Carlos O'Donell
2016-10-31 18:38 ` [PATCH v3] " Steve Ellcey
2016-10-31 19:50 ` Carlos O'Donell
2016-10-31 19:57 ` Steve Ellcey
2016-10-31 20:50 ` Carlos O'Donell
2016-10-31 21:00 ` Steve Ellcey
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=VI1PR0801MB2031D3CA18A8EEF0340AB3A9FFA10@VI1PR0801MB2031.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=Bin.Cheng@arm.com \
--cc=carlos@redhat.com \
--cc=davem@davemloft.net \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=schwab@linux-m68k.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).