From: Paul Mackerras <paulus@samba.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] fix gcc4 warning in asm-ppc/time.h
Date: Fri, 5 Aug 2005 08:19:04 +1000 [thread overview]
Message-ID: <17138.37976.125149.720836@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20050803221517.21b54d7e.akpm@osdl.org>
Andrew Morton writes:
> Do we really want to do this? The above implies that mfspr(SPRN_PVR) will
> return the same value across the entire uptime of the kernel. Is that
> true?
Yes, the PVR is the processor version register, and it would be quite
disturbing if the silicon changed underneath us. :)
> Why is this function paying with const anyway?
It seemed like a good idea at the time? :)
Paul.
next prev parent reply other threads:[~2005-08-04 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 9:55 [PATCH] fix gcc4 warning in asm-ppc/time.h Christoph Hellwig
2005-08-04 5:15 ` Andrew Morton
2005-08-04 5:54 ` Gabriel Paubert
2005-08-04 9:46 ` Benjamin Herrenschmidt
2005-08-04 10:19 ` Gabriel Paubert
2005-08-04 22:19 ` Paul Mackerras [this message]
2005-08-04 5:17 ` Andrew Morton
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=17138.37976.125149.720836@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).