Kalle Valo <kvalo@xxxxxxxxxx> writes: > "Jason A. Donenfeld" <Jason@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxx> >> Cc: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> >> Cc: Stanislaw Gruszka <stf_xl@xxxxx> >> Cc: Helmut Schaa <helmut.schaa@xxxxxxxxxxxxxx> >> Cc: Kalle Valo <kvalo@xxxxxxxxxx> >> Signed-off-by: Jason A. Donenfeld <Jason@xxxxxxxxx> >> Acked-by: Stanislaw Gruszka <stf_xl@xxxxx> > > 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
