From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Revert "break build if it would produce broken binary"
Date: Wed, 1 Jul 2015 15:37:15 +0200 [thread overview]
Message-ID: <20150701153715.30cd7785@lilith> (raw)
In-Reply-To: <20150603071812.GA12854@amd>
Hello Pavel,
On Wed, 3 Jun 2015 09:18:12 +0200, Pavel Machek <pavel@denx.de> wrote:
> On Tue 2015-06-02 13:13:05, Tom Rini wrote:
> > On Tue, Jun 02, 2015 at 11:08:21AM -0600, Simon Glass wrote:
> >
> > > The root cause of this problem should now be fixed.
> > >
> > > This reverts commit a6a4c542d316b3401f0840ac5378743191bca851.
> > > Signed-off-by: Simon Glass <sjg@chromium.org>
> >
> > Thanks for digging into all of this! Pavel, can you confirm that with
> > these two applied things work still? Thanks!
>
> For series:
>
> Acked-by: Pavel Machek <pavel@denx.de>
> Tested-by: Pavel Machek <pavel@denx.de>
Do we consider this a bug fix? If so, I can add this series it to my
ARM PR (along with Masahiro's 'enable CONFIG_USE_PRIVATE_LIBGCC by
default' which was clashing with (here reverted) a6a4c542d.
> Thanks,
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-07-01 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 17:08 [U-Boot] [PATCH 1/2] arm: Add ENTRY/ENDPROC to private libgcc functions Simon Glass
2015-06-02 17:08 ` [U-Boot] [PATCH 2/2] Revert "break build if it would produce broken binary" Simon Glass
2015-06-02 17:13 ` Tom Rini
2015-06-03 7:18 ` Pavel Machek
2015-07-01 13:37 ` Albert ARIBAUD [this message]
2015-07-01 13:54 ` Tom Rini
2015-07-01 13:54 ` Pavel Machek
2015-07-01 14:11 ` Albert ARIBAUD
2015-07-01 14:11 ` [U-Boot] [PATCH 1/2] arm: Add ENTRY/ENDPROC to private libgcc functions Albert ARIBAUD
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=20150701153715.30cd7785@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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