From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: next pass of cleaning up micropatch.c
Date: Sat, 09 Oct 2004 00:32:38 +0200 [thread overview]
Message-ID: <20041008223243.7D84CC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 08 Oct 2004 16:46:26 EDT." <Pine.LNX.4.60.0410081643100.25430@dell.enoriver.com>
In message <Pine.LNX.4.60.0410081643100.25430@dell.enoriver.com> you wrote:
>
> nice idea, but sadly, doomed to failure. note that the code to copy
> the patch arrays *requires* you to be able to take the sizeof() those
> arrays to know *exactly* how much to copy. if you pass the array to a
> function by its address, i'm pretty sure you lose the ability to take
> its sizeof() anymore, isn't that right?
This is not right. Guess how memcpy() works - it's a function, btw.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
God runs electromagnetics by wave theory on Monday, Wednesday, and
Friday, and the Devil runs them by quantum theory on Tuesday, Thurs-
day, and Saturday. -- William Bragg
next prev parent reply other threads:[~2004-10-08 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 12:44 next pass of cleaning up micropatch.c Robert P. J. Day
2004-10-08 15:34 ` Dan Malek
2004-10-08 15:46 ` Tom Rini
2004-10-08 15:45 ` Robert P. J. Day
2004-10-08 16:02 ` Tom Rini
2004-10-08 16:14 ` Robert P. J. Day
2004-10-08 16:35 ` Dan Malek
2004-10-08 20:46 ` Robert P. J. Day
2004-10-08 22:32 ` Wolfgang Denk [this message]
2004-10-08 23:10 ` Robert P. J. Day
2004-10-08 23:29 ` Wolfgang Denk
2004-10-08 23:33 ` Robert P. J. Day
2004-10-08 23:56 ` Wolfgang Denk
2004-10-08 23:53 ` Robert P. J. Day
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=20041008223243.7D84CC1430@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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).