linux-kernel - Differences in bitops argument types

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071101222305.GA28830@duck.suse.cz>
Date:	Thu, 1 Nov 2007 23:23:05 +0100
From:	Jan Kara <jack@...e.cz>
To:	linux-kernel@...r.kernel.org
Subject: Differences in bitops argument types

  Hello,

  I've just found out that operations like constant_test_bit() take pointer
of different types on different architectures. In particular, x86_64,
blackfin and frv take void * while i386, s390 and m68k take unsigned long
*. Is this intended difference? Wouldn't using void * everywhere be more
appropriate? Thanks for answer in advance.

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