From: Andre' Draszik <andid@gmx.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH][PPC32] mktree fix
Date: Fri, 11 Feb 2005 09:37:26 +0100 [thread overview]
Message-ID: <420C6EC6.4020800@gmx.net> (raw)
In-Reply-To: <20050208223348.GA31592@smtp.west.cox.net>
Tom Rini wrote:
> On Mon, Feb 07, 2005 at 05:34:36AM +0100, Andre' Draszik wrote:
>
>
>>This one fixes mktree. The image size stored in the header is pretty off
>>without
>>this patch. (yes, it can make a difference of upto almost 64k)
>>
>>Signed-off-by: Andre' Draszik <andid@gmx.net>
>
>
> With this wrong, what breaks? Thanks.
I don't think anything breaks but if somebody relies on the image size
stored in the header, up to almost 64k bytes of flash could be wasted.
a.
next prev parent reply other threads:[~2005-02-11 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 4:34 [PATCH][PPC32] mktree fix Andre' Draszik
2005-02-08 22:33 ` Tom Rini
2005-02-11 8:37 ` Andre' Draszik [this message]
2005-02-11 15:20 ` 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=420C6EC6.4020800@gmx.net \
--to=andid@gmx.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).