From: Todd Inglett <tinglett@vnet.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bitops porting question
Date: Tue, 21 Nov 2000 10:10:16 -0600 [thread overview]
Message-ID: <3A1A9E68.E1BD9072@vnet.ibm.com> (raw)
In-Reply-To: 20001121152056.A21375@gruyere.muc.suse.de
Andi Kleen wrote:
>
> iirc David Miller did a big sweep of such things in the generic source
> when doing the sparc64 port which has exactly the same problem.
> To make sure you should probably define the macro so that you get
> a warning for &flags being anything that unsigned long, e.g. using
> a inline with a prototype and do a regular grep of the tree if anything
> shows these warnings.
Cool. I was hoping sparc64 cleaned some of this up. I don't read sparc
asm very well and for lack of comments in sparc64's bitops.S I wasn't
sure if it went 64 bit or not. I'll change the prototypes to catch
offenders.
BTW, it appears to be working.
--
-todd
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-11-21 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 12:44 bitops porting question Todd Inglett
2000-11-21 13:44 ` Todd Inglett
2000-11-21 14:20 ` Andi Kleen
2000-11-21 16:10 ` Todd Inglett [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=3A1A9E68.E1BD9072@vnet.ibm.com \
--to=tinglett@vnet.ibm.com \
--cc=ak@suse.de \
--cc=linuxppc-dev@lists.linuxppc.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).