linux-kernel - Re: Commit 085219f79cad broke Sparc-32 back in 2.6.28.

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100326.203745.04177541.davem@davemloft.net>
Date:	Fri, 26 Mar 2010 20:37:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rob@...dley.net
Cc:	blauwirbel@...il.com, linux-kernel@...r.kernel.org
Subject: Re: Commit 085219f79cad broke Sparc-32 back in 2.6.28.

From: Rob Landley <rob@...dley.net>
Date: Fri, 26 Mar 2010 22:35:47 -0500

> What exactly was the problem with just saying "unsigned short" when you mean 
> an unsigned short?  The way x86 does, and arm?  (If these ever change, it 
> breaks binary compatability.  Not sure what these changes were trying to 
> accomplish...)

I was trying to use well defined types that described the
usage and the origin of the definition.

I'm happy to use "unsigned short" or whatever works better.
Please send a patch.
--
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/