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 v3] Fix initrd length miscalculation in bootm command when using a dtu
Date: Fri, 04 May 2007 11:32:34 -0500	[thread overview]
Message-ID: <463B6022.7000908@freescale.com> (raw)
In-Reply-To: <20070504162710.691AE353AF1@atlas.denx.de>

Wolfgang Denk wrote:
> In message <463B3463.1030702@freescale.com> you wrote:
>> If you apply my patch, then the comment becomes correct.  My goal was to 
>> lock the variables 'len' and 'data' into one purpose.  The reason the 
> 
> I think you actually missed a few places where len was also used.

Really?  I doubt it.  Every other place that len is used, it's the initrd length.  Can you 
show me where that's not the case?

>> bug existed is because the other developer didn't realize this.  He used 
>> 'len' thinking it was available.  In a sense, I was trying to implement 
> 
> This type of thinking  was  plain  wrong.  You  must  never  use  any
> variable without understanding what it's being used for.

You're absolutely right, which is why *I* don't make that mistake.  But some one else did, 
and someone else might again.  do_bootm_linux() is hideous code, and it just gets worse 
and worse.  Frankly, anyone trying to modify that code needs all the help he can get!

> As I explained before, you need a  normal  developer's  repo,  not  a
> guardian  one.  And I repeat: I offer you such a repo, it's available
> right now, I just need the IP address from where you will connect.

It would be the same IP address that Kim, Andy, and Jon use.  As soon as I get hold of one 
of them, I'll ask, but technically you should know the answer already.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-05-04 16:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 22:30 [U-Boot-Users] [PATCH v3] Fix initrd length miscalculation in bootm command when using a dtu Timur Tabi
2007-05-03 23:47 ` Wolfgang Denk
2007-05-04  1:13   ` Timur Tabi
2007-05-04  8:28     ` Wolfgang Denk
2007-05-04 13:25       ` Timur Tabi
2007-05-04 13:46         ` Stefan Roese
2007-05-04 14:22           ` Jerry Van Baren
2007-05-04 16:02             ` Timur Tabi
2007-05-04 16:07               ` Jerry Van Baren
2007-05-04 15:57           ` Timur Tabi
2007-05-04 16:27         ` Wolfgang Denk
2007-05-04 16:32           ` Timur Tabi [this message]
2007-05-04 19:28             ` Wolfgang Denk
2007-05-04 19:40               ` Timur Tabi
2007-05-04 21:58               ` 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=463B6022.7000908@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