[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r0z11x50.fsf@kernel.org>
Date: Fri, 21 Oct 2022 09:58:03 +0300
From: Kalle Valo <kvalo@...nel.org>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Stanislaw Gruszka <stf_xl@...pl>,
Helmut Schaa <helmut.schaa@...glemail.com>
Subject: Re: [PATCH v3] wifi: rt2x00: use explicitly signed or unsigned types
Kalle Valo <kvalo@...nel.org> writes:
> "Jason A. Donenfeld" <Jason@...c4.com> 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 <akpm@...ux-foundation.org>
>> Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>> Cc: Stanislaw Gruszka <stf_xl@...pl>
>> Cc: Helmut Schaa <helmut.schaa@...glemail.com>
>> Cc: Kalle Valo <kvalo@...nel.org>
>> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
>> Acked-by: Stanislaw Gruszka <stf_xl@...pl>
>
> 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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists