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 10:57:15 -0500 [thread overview]
Message-ID: <463B57DB.1020201@freescale.com> (raw)
In-Reply-To: <200705041546.13452.sr@denx.de>
Stefan Roese wrote:
> You have a point with your variable usage "restriction", and Wolfgang has a
> point with the "readability" of your patch as it doesn't really tell what is
> fixed without read the current source. Could be that your implementation is
> the "better" one, but the patch Wolfgang applied was just less intrusive.
Well, I can't argue with that.
> No, we shouldn't "fork" the code here. Let's focus on the other open issues.
Since you bring it up, I submitted a patch for the 5xxx platform many months ago. How do
I get that applied? The patch is here:
http://sourceforge.net/mailarchive/message.php?msg_id=117131648887-git-send-email-timur%40freescale.com
> You mention other bugs introduced by the libfdt code above. ;-)
Jerry is already aware of them and working on fixes.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-04 15:57 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 [this message]
2007-05-04 16:27 ` Wolfgang Denk
2007-05-04 16:32 ` Timur Tabi
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=463B57DB.1020201@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 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.