From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "Align global_data to a 16-byte boundary"
Date: Mon, 17 Aug 2015 20:53:55 -0400 [thread overview]
Message-ID: <20150818005355.GG25532@bill-the-cat> (raw)
In-Reply-To: <1439825324-32224-1-git-send-email-sjg@chromium.org>
On Mon, Aug 17, 2015 at 09:28:44AM -0600, Simon Glass wrote:
> This causes widespread breakage due to the operation of the low-level code
> in crt0.S and cro0_64.S for ARM at least.
>
> The fix is not complicated but it seems safer to revert this for now.
>
> This reverts commit 2afddae07523f23f77acd066ad1719f53d289f98.
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150817/22deda34/attachment.sig>
next prev parent reply other threads:[~2015-08-18 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 15:28 [U-Boot] [PATCH] Revert "Align global_data to a 16-byte boundary" Simon Glass
2015-08-18 0:53 ` Tom Rini [this message]
2015-08-18 8:49 ` Sergei Temerkhanov
2015-08-18 12:44 ` Simon Glass
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=20150818005355.GG25532@bill-the-cat \
--to=trini@konsulko.com \
--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