Re: i386 and x86-64 bitops function prototypes differ

> 
> So I'd say that x86_64 is wrong, and should be changed to take ulong*.

I'm trying to remember why I used void * -- I think there was a reason,
but it's lost in the myst of time.

Anyways, I suspect changing it now would have quite some fallout on other
code, but hopefully limited to arch/x86_64/*. But fixing these up
will hopefully not be too hard. 

-Andi



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • i386 and x86-64 bitops function prototypes differ
    • From: Stephane Eranian <[email protected]>
  • Re: i386 and x86-64 bitops function prototypes differ
    • From: Stephane Eranian <[email protected]>
  • Re: i386 and x86-64 bitops function prototypes differ
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH 4 of 4] Introduce aio system call submission and completion system calls
• Next by Date: Re: [patch 0/9] x86_64: reliable TSC-based gettimeofday
• Previous by thread: Re: i386 and x86-64 bitops function prototypes differ
• Next by thread: [PATCH] bonding: ARP monitoring broken on x86_64
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]