All of
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <>
To: Nathan Chancellor <>
Cc: Sasha Levin <>,,,
	Nick Desaulniers <>
Subject: Re: Patches for clang and CONFIG_WERROR (arm64/x86_64)
Date: Fri, 14 Jan 2022 06:47:49 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YeCpzLnfA+g+u3Id@archlinux-ax161>

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

      reply	other threads:[~2022-01-14  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 22:38 Patches for clang and CONFIG_WERROR (arm64/x86_64) Nathan Chancellor
2022-01-14  5:47 ` Greg Kroah-Hartman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.