From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored
Date: Sat, 22 Jan 2011 19:03:56 +0100 [thread overview]
Message-ID: <4D3B1C0C.4040805@free.fr> (raw)
In-Reply-To: <4D3B1679.20003@googlemail.com>
Hi Dirk,
Le 22/01/2011 18:40, Dirk Behme a ?crit :
> On 22.01.2011 13:46, Alexander Holler wrote:
>> A patch for write?() and read?() is currently in the
>> u-boot-arm-repository (but not in the master and not in 2010.12):
>>
>> http://lists.denx.de/pipermail/u-boot/2011-January/084885.html
>
> What's about pulling it sooner than later into master, then?
I will send out a pull request for u-boot-arm once I have applied all
outstanding ARM patches from jan 17 or before and all outstanding ARM
bug fixes regardless of their date, and pulled other ARM repos whose
custodian requests pulling.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-01-22 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 12:46 [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored Alexander Holler
2011-01-22 14:14 ` Wolfgang Denk
2011-01-22 17:40 ` Dirk Behme
2011-01-22 18:03 ` Albert ARIBAUD [this message]
2011-01-22 19:30 ` Wolfgang Denk
2011-01-22 20:23 ` Albert ARIBAUD
2011-01-24 13:03 ` Wolfgang Denk
2011-01-24 18:18 ` Albert ARIBAUD
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=4D3B1C0C.4040805@free.fr \
--to=albert.aribaud@free.fr \
--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