From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix use of "void *" for block dev read/write buffer pointers
Date: Fri, 13 Apr 2007 12:22:57 -0500 [thread overview]
Message-ID: <461FBC71.2030300@freescale.com> (raw)
In-Reply-To: <200704130845.32830.d.peter@mpl.ch>
Denis Peter wrote:
> My patch from April, 2nd, fixes this issue already. In my patch I decided to just
> cast the pointer back to ulong *, since I don't know if it is a good idea to increment
> a pointer to void *.
It's not part of the normal C standard, but gcc allows you to perform pointer math on a
void *. It acts as is it were a "u8 *".
Remember, this code:
ulong *p;
p++;
Has the same effect as:
void *p
p += sizeof(ulong);
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-04-13 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 15:28 [U-Boot-Users] [PATCH] Fix use of "void *" for block dev read/write buffer pointers Greg Lopp
2007-04-12 16:33 ` Grant Likely
2007-04-12 19:07 ` Greg Lopp
2007-04-12 19:49 ` Grant Likely
2007-04-12 20:03 ` Greg Lopp
[not found] ` <1176408946.14027.41.camel@saruman.qstreams.net>
2007-04-12 20:25 ` Grant Likely
2007-04-12 20:27 ` Grant Likely
2007-04-13 5:56 ` Stefan Roese
2007-04-13 6:45 ` Denis Peter
2007-04-13 6:54 ` Grant Likely
2007-04-13 7:18 ` Stefan Roese
2007-04-13 11:19 ` Denis Peter
2007-04-13 17:22 ` Timur Tabi [this message]
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=461FBC71.2030300@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.