From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch] Clean up lvalues in two places for gcc 4.0
Date: Thu, 13 Oct 2005 07:37:38 -0400 [thread overview]
Message-ID: <434E4702.6020203@smiths-aerospace.com> (raw)
Hi Wolfgang,
Attached is a patch I did last night (2005-10-12) to fix two places
where gcc 4.0 refused to compile due to the lvalue constructs no longer
being supported. The patches compile, I have not executed the resulting
code: please double-check for correctness.
fs/jffs2/compr_rubin.c | 3 ++-
net/net.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
---- Changelog ----
Clean up lvalue issues for gcc 4.0
Patch by Jerry Van Baren, 12 October 2005
Signed-off-by: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
----
Best regards,
gvb
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-lvalues-submitted-2005-10-13.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20051013/8f50c27e/attachment.txt
next reply other threads:[~2005-10-13 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 11:37 Jerry Van Baren [this message]
2005-10-13 14:52 ` [U-Boot-Users] [Patch] Clean up lvalues in two places for gcc 4.0 Wolfgang Denk
2005-10-13 15:11 ` Jerry Van Baren
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=434E4702.6020203@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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