From: Bernhard Nortmann <bernhard.nortmann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] sunxi: Increase SPL header size to 64 bytes to avoid code corruption
Date: Fri, 3 Jun 2016 09:30:03 +0200 [thread overview]
Message-ID: <575131FB.1060005@web.de> (raw)
In-Reply-To: <20160602175721.4a41bd20@i7>
Am 02.06.2016 um 16:57 schrieb Siarhei Siamashka:
> On Mon, 16 May 2016 19:52:33 +0200
> Hans de Goede <hdegoede@redhat.com> wrote:
>
>> [...]
>> Other then that worry, I see no problem with adding a
>> fel_script_length, Siarhei what is your opinion on this ?
> I personally have no objections.
>
Does it make sense if I submit a patch for this, or should we simply
squash that one-line change into your "Store the device tree name in
the SPL header" series?
Regards, B. Nortmann
next prev parent reply other threads:[~2016-06-03 7:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 1:13 [U-Boot] [PATCH v2] sunxi: Increase SPL header size to 64 bytes to avoid code corruption Siarhei Siamashka
2016-05-15 10:04 ` Hans de Goede
2016-05-16 9:56 ` Bernhard Nortmann
2016-05-16 17:52 ` Hans de Goede
2016-06-02 14:57 ` Siarhei Siamashka
2016-06-03 7:30 ` Bernhard Nortmann [this message]
2016-06-03 10:53 ` Hans de Goede
2016-06-04 17:12 ` [U-Boot] [PATCH] sunxi: Add the ability to pass (script) filesize in the SPL header Bernhard Nortmann
2016-06-05 11:44 ` Siarhei Siamashka
2016-06-05 13:01 ` Bernhard Nortmann
2016-06-06 9:20 ` Siarhei Siamashka
2016-06-07 14:09 ` Bernhard Nortmann
2016-06-07 17:14 ` Siarhei Siamashka
2016-06-08 18:23 ` [U-Boot] [PATCH v2] sunxi: Add the ability to recognize and auto-import uEnv-style data Bernhard Nortmann
2016-06-08 20:13 ` Hans de Goede
2016-06-08 21:29 ` Bernhard Nortmann
2016-06-09 0:14 ` Siarhei Siamashka
2016-06-09 5:37 ` [U-Boot] [PATCH v3] sunxi: FEL - " Bernhard Nortmann
2016-06-10 19:31 ` [U-Boot] [U-Boot, " Hans de Goede
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=575131FB.1060005@web.de \
--to=bernhard.nortmann@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.