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]
Date:   Fri, 21 Oct 2022 09:58:03 +0300
From:   Kalle Valo <>
To:     "Jason A. Donenfeld" <>
        Andrew Morton <>,
        Andy Shevchenko <>,
        Stanislaw Gruszka <>,
        Helmut Schaa <>
Subject: Re: [PATCH v3] wifi: rt2x00: use explicitly signed or unsigned types

Kalle Valo <> writes:

> "Jason A. Donenfeld" <> wrote:
>> On some platforms, `char` is unsigned, but this driver, for the most
>> part, assumed it was signed. In other places, it uses `char` to mean an
>> unsigned number, but only in cases when the values are small. And in
>> still other places, `char` is used as a boolean. Put an end to this
>> confusion by declaring explicit types, depending on the context.
>> Cc: Andrew Morton <>
>> Cc: Andy Shevchenko <>
>> Cc: Stanislaw Gruszka <>
>> Cc: Helmut Schaa <>
>> Cc: Kalle Valo <>
>> Signed-off-by: Jason A. Donenfeld <>
>> Acked-by: Stanislaw Gruszka <>
> Patch applied to wireless.git, thanks.
> 3347d22eb90b wifi: rt2x00: use explicitly signed or unsigned types

Please disregard this commit id, I used a wrong baseline so I need to
apply this again.


Powered by blists - more mailing lists