public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command
Date: Tue, 06 Feb 2007 09:11:21 -0600	[thread overview]
Message-ID: <45C89A99.8070709@freescale.com> (raw)
In-Reply-To: <20070206004307.D7C18353AF8@atlas.denx.de>

Wolfgang Denk wrote:
> In message <11707043793601-git-send-email-timur@freescale.com> you wrote:
>> The do_bootm_linux() function was using the same variable ('len') to calculate
>> the the dtu length and the initrd length, which meant that the initrd length
>> was incorrect.  This patch creates renames 'len' and 'data' to 'initrd_len'
>> and 'initrd_data', thereby preventing any future confusion.  It also deletes
>> 'len' and 'data' because the dtu calculations don't actually need them.
> 
> I can't parse this. 'len' was used twice, but actually it wasn't used
> in the second case, but you renamed the only remaining use it had?

Sorry, it looks like I have a few typos in my description.  Here's a new one:

"The do_bootm_linux() function was using the same variable ('len') to calculate 
the dtu length and the initrd length.  This meant that the initrd length was 
incorrect when it came time to book the kernel.  This resulted in the inability 
to boot with an initrd on an OF-based kernel.  This patch renames the local 
variables 'len' and 'data' to 'initrd_len' and 'initrd_data', respectively, and 
it uses initrd_len and initrd_data only for initrd calculations.

In addition, there were a few places where 'len' and 'data' where being used as 
temporary variables.  The code was modified to eliminate the need for temporary 
variables."

Does this explain everything?  Do you want me to resubmit the patch with the new 
changelog text?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-02-06 15:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 19:39 [U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command Timur Tabi
2007-02-06  0:43 ` Wolfgang Denk
2007-02-06 15:11   ` Timur Tabi [this message]
2007-02-06 17:07     ` Kumar Gala
2007-02-06 17:11       ` Timur Tabi
2007-02-06 17:14         ` Kumar Gala
2007-02-06 17:17           ` Timur Tabi
2007-02-19 23:51           ` Timur Tabi
2007-02-20 16:14             ` Kumar Gala
2007-02-20 16:36               ` Timur Tabi
2007-02-20 19:06                 ` Wolfgang Denk
2007-02-20 19:19                   ` Timur Tabi
2007-02-20 23:05                   ` Timur Tabi
2007-02-26 13:10                     ` Wolfgang Denk
2007-02-26 16:15                       ` Timur Tabi
2007-02-27 16:48                       ` Timur Tabi
2007-02-27 20:55                         ` Wolfgang Denk
2007-02-27 22:13                           ` Timur Tabi
2007-03-16 21:49                             ` Timur Tabi
2007-03-23 22:44                               ` Johns Daniel
2007-03-27 16:25                                 ` Johns Daniel
2007-03-27 16:30                                   ` Timur Tabi

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=45C89A99.8070709@freescale.com \
    --to=timur@freescale.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