Re: [PATCH] Get rid of non portable _syscall0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lon Hohberger wrote:
>
> Ok, so, I'll add a #warn and return pthread_self() for now - since it
> also doesn't fail and returns a thread-specific identifier (which is the
> primary reason we used gettid()...).

Sounds reasonable to me.

>> (many of which don't have _syscall magic macros, and word on the street
>> is that we may not have them on any arches in the future).
>
> That can only be a good thing.

Amen, and preach on.  The more magic numbers we can get rid of, the better.

... Adam


--

Linux-cluster@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux