linux-kernel - Re: [PATCH] staging: octeon: type change from uint<bits>

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: <aYsLZcRhZ7kB7f51@stanley.mountain>
Date: Tue, 10 Feb 2026 13:41:41 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: David Laight <david.laight.linux@...il.com>
Cc: Yoelvis Oliveros <yoelvisoliveros@...il.com>,
	gregkh@...uxfoundation.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org, outreachy@...ts.linux.dev
Subject: Re: [PATCH] staging: octeon: type change from uint<bits>_t to u<bits>

On Tue, Feb 10, 2026 at 10:19:52AM +0000, David Laight wrote:
> As a separate issue, what is the purpose of all these bit-field structures?
> You can't portably use C bit-fields to map hardware registers or network
> packets.
> It isn't just byte-order, the 'bit order' can differ even for the same
> endianness.

Huh.  I didn't know that.  Can you give an example?

regards,
dan carpenter