From: Holger Schurig <holgerschurig@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] AM335x: MLO image issue
Date: Tue, 24 Mar 2015 09:30:29 +0100 [thread overview]
Message-ID: <CAOpc7mEFF7R=dhjS8YONJgLAH_zM+AZrYjZX2xhEX2Dbuk+owg@mail.gmail.com> (raw)
In-Reply-To: <20150324063015.GR9742@pengutronix.de>
Sascha,
AFAIK he implemented two patches from Torvald's linux kernel git tree:
* af958a38a60c7ca3d8a39c918c1baa2ff7b6b233 removes a broken
check-for-integer-overflow method
* 72cf90124e87d975d0b2114d930808c58b4c05e4 add's a new
make-sure-integers-dont-overflow logic, which is also marked as "put
it into stable kernels"
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-03-24 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 15:17 Teresa Gámez
2015-03-23 15:17 ` [PATCH] lib/lzo: port lzo fix from upstream kernel Teresa Gámez
2015-03-24 8:26 ` Holger Schurig
2015-03-24 6:30 ` [PATCH] AM335x: MLO image issue Sascha Hauer
2015-03-24 8:30 ` Holger Schurig [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='CAOpc7mEFF7R=dhjS8YONJgLAH_zM+AZrYjZX2xhEX2Dbuk+owg@mail.gmail.com' \
--to=holgerschurig@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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