From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc 4.8.2: arm fixes for stack corruption
Date: Mon, 27 Jan 2014 09:23:23 +0100 [thread overview]
Message-ID: <87eh3tzvd0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140124151119.GA27232@gmail.com> (Andrew Ruder's message of "Fri, 24 Jan 2014 09:11:19 -0600")
>>>>> "Andrew" == Andrew Ruder <andrew.ruder@elecsyscorp.com> writes:
> This seems to especially affect the kernel, but in an
> interrupt-heavy system, this fixes a bug that can cause frequent
> NULL pointer dereference crashes on ARM systems.
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-01-27 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 15:11 [Buildroot] [PATCH] gcc 4.8.2: arm fixes for stack corruption Andrew Ruder
2014-01-27 8:23 ` Peter Korsgaard [this message]
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=87eh3tzvd0.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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