Patches for clang and CONFIG_WERROR (arm64/x86_64)

Patches for clang and CONFIG_WERROR (arm64/x86_64)

[Nathan Chancellor]

Hi Greg and Sasha,

Please consider applying the following commits to allow arm64 and x86_64
allmodconfig to compile with CONFIG_WERROR enabled with clang-11 through
clang-14 (the currently supported releases upstream).

502408a61f4b ("staging: wlan-ng: Avoid bitwise vs logical OR warning in hfa384x_usb_throttlefn()") [5.15, 5.10, 5.4, 4.19, 4.14, 4.9]
2e70570656ad ("drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()") [5.16, 5.15, 5.10, 5.4, 4.19, 4.14, 4.9, 4.4]
144779edf598 ("staging: greybus: fix stack size warning with UBSAN") [5.16, 5.15, 5.10, 5.4]

I primarily care about 5.16 and 5.15, as those are the releases that
have CONFIG_WERROR, but I included all the versions that those patches
should apply cleanly to, as they do fix warnings in the build that
people might see, although I don't think they are worth backporting
further manually until someone complains. 502408a61f4b is already in
5.16.

If there are any issues or objections, please let me know!

Cheers,
Nathan

Re: Patches for clang and CONFIG_WERROR (arm64/x86_64)

[Greg Kroah-Hartman]

On Thu, Jan 13, 2022 at 03:38:04PM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
> 
> Please consider applying the following commits to allow arm64 and x86_64
> allmodconfig to compile with CONFIG_WERROR enabled with clang-11 through
> clang-14 (the currently supported releases upstream).
> 
> 502408a61f4b ("staging: wlan-ng: Avoid bitwise vs logical OR warning in hfa384x_usb_throttlefn()") [5.15, 5.10, 5.4, 4.19, 4.14, 4.9]
> 2e70570656ad ("drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()") [5.16, 5.15, 5.10, 5.4, 4.19, 4.14, 4.9, 4.4]
> 144779edf598 ("staging: greybus: fix stack size warning with UBSAN") [5.16, 5.15, 5.10, 5.4]
> 
> I primarily care about 5.16 and 5.15, as those are the releases that
> have CONFIG_WERROR, but I included all the versions that those patches
> should apply cleanly to, as they do fix warnings in the build that
> people might see, although I don't think they are worth backporting
> further manually until someone complains. 502408a61f4b is already in
> 5.16.

All now queued up, thanks.

greg k-h