On 5/15/21 9:01 PM, Alejandro Colomar wrote:
Some manual pages are already using C99 syntax for integral
types 'uint32_t', but some aren't. There are some using kernel
syntax '__u32'. Fix those.
Both the kernel and the standard types are 100% binary compatible,
and the source code differences
Hi Daniel,
On 5/4/21 10:06 PM, Daniel Borkmann wrote:
On 5/4/21 6:08 PM, Daniel Borkmann wrote:
>
> But what /problem/ is this really solving? Why bother to change
this /now/
> after so many years?! I think this is causing more confusion than
solving
> anything, really. Moreover, what ar
Hi Florian,
On 5/4/21 9:45 PM, Florian Weimer wrote:
* Alejandro Colomar:
The thing is, in all of those threads, the only reasons to avoid
types in the kernel (at least, the only explicitly
mentioned ones) are (a bit simplified, but this is the general idea of
those threads):
* Possibly brea
Hi Greg, Daniel,
On 5/4/21 6:06 PM, Greg KH wrote:
> There's a very old post from Linus where he describes the difference
> between things like __u32 and uint32_t. They are not the same, they
> live in different namespaces, and worlds, and can not always be swapped
> out for each other on all ar
Hi Greg and Alexei,
On Tue, May 04, 2021 at 07:12:01AM -0700, Alexei Starovoitov wrote:
For the same reasons as explained earlier:
Nacked-by: Alexei Starovoitov
Okay, I'll add that.
On 5/4/21 4:24 PM, Greg KH wrote:> I agree, the two are not the same
type at all, this change should not be
Hi Joseph,
On 4/26/21 7:19 PM, Joseph Myers wrote:
On Sat, 24 Apr 2021, Alejandro Colomar via Libc-alpha wrote:
Some pages also document attributes, using GNU syntax
'__attribute__((xxx))'. Update those to use the shorter and more
portable C2x syntax, which hasn't been standardized yet, but i
Hello Alexei,
On 4/24/21 1:20 AM, Alexei Starovoitov wrote:
Nack.
The man page should describe the kernel api the way it is in .h file.
Why?
When glibc uses __size_t (or any other non-standard types) just because
the standard doesn't allow it to define some types in some specific
header, th
Ping
On 12/15/20 2:30 PM, Alejandro Colomar wrote:
> Reported-by: Heinrich Schuchardt
> Signed-off-by: Alejandro Colomar
> Cc: Martin Sebor
> Cc: Dave Martin
> ---
>
> v6:
> - GCC has always exposed 'void *', as Martin Sebor noted.
> It's Clang (and maybe others) that (following GCC's docs)