From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Fix gcc 4 warnings on ia64
Date: Wed, 17 Aug 2005 00:11:44 +0000 [thread overview]
Message-ID: <20050817001144.GA3996@wotan.suse.de> (raw)
In-Reply-To: <20050816155747.GN20749@wotan.suse.de>
On Tue, Aug 16, 2005 at 05:05:42PM -0700, Luck, Tony wrote:
>
> > You actually need the const attribute on __ia64_get_io_port_base
>
> cscope didn't show any users of this function ... so I thought
> perhaps the callers were in some macros that concatenated
> strings with ## to make the name, but I couldn't see any.
You also need to fix the other function which had a bogus volatile.
BTW I bet the rationale in mmu.h for the volatile is bogus.
-Andi
next prev parent reply other threads:[~2005-08-17 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 15:57 [PATCH] Fix gcc 4 warnings on ia64 Andi Kleen
2005-08-16 23:04 ` Peter Chubb
2005-08-16 23:34 ` Andi Kleen
2005-08-17 0:05 ` Luck, Tony
2005-08-17 0:11 ` Andi Kleen [this message]
2005-08-17 1:30 ` david mosberger
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=20050817001144.GA3996@wotan.suse.de \
--to=ak@suse.de \
--cc=linux-ia64@vger.kernel.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