All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, RFC] SPL: FIT: Align loading address for header
Date: Tue, 31 May 2016 19:42:42 +0530	[thread overview]
Message-ID: <574D9BDA.608@ti.com> (raw)
In-Reply-To: <20160531140911.GE7419@bill-the-cat>



On Tuesday 31 May 2016 07:39 PM, Tom Rini wrote:
> On Tue, May 31, 2016 at 09:59:47AM +0530, Lokesh Vutla wrote:
>>
>>
>> On Monday 30 May 2016 11:26 PM, Tom Rini wrote:
>>> On Thu, Apr 28, 2016 at 10:36:11AM +0200, Michal Simek wrote:
>>>
>>>> If bl_len is not aligned it can caused a problem because another code
>>>> expects that start is aligned.
>>>>
>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>> Reviewed-by: Simon Glass <sjg@chromium.org>
>>>
>>> Applied to u-boot/master, thanks!
>>
>> This patch is not required and should not be applied.
> 
> Did you both agree on "spl: Allow to load a FIT containing U-Boot from
> FS" instead then?  And thus what's in the tree needs a little re-work
> since I made the above apply on top of this one instead?  Sorry/thanks!

Yes, Michal as well agreed that this is not required[1]. This patch
might work but it can fail in corner cases.

If you want I can send a fix patch on top of latest.

[1] http://patchwork.ozlabs.org/patch/616065/

Thanks and regards,
Lokesh

> 

  reply	other threads:[~2016-05-31 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  8:36 [U-Boot] [RFC PATCH] SPL: FIT: Align loading address for header Michal Simek
2016-05-01 18:54 ` Simon Glass
2016-05-02  3:46 ` Lokesh Vutla
2016-05-02  7:53   ` Michal Simek
2016-05-30 17:56 ` [U-Boot] [U-Boot, RFC] " Tom Rini
2016-05-31  4:29   ` Lokesh Vutla
2016-05-31 14:09     ` Tom Rini
2016-05-31 14:12       ` Lokesh Vutla [this message]
2016-05-31 14:15         ` Tom Rini

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=574D9BDA.608@ti.com \
    --to=lokeshvutla@ti.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 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.