All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>,
	llvm@lists.linux.dev
Subject: Warning fixes for clang + x86_64 allmodconfig on 5.10 and 5.4
Date: Tue, 10 May 2022 10:49:16 -0700	[thread overview]
Message-ID: <YnqlnFWCrEz11T5Y@dev-arch.thelio-3990X> (raw)

Hi Greg and Sasha,

A recent change in LLVM [1] strengthened -Wenum-conversion, which
revealed a couple of instances in 5.10 and 5.4 (the oldest release that
I personally build test). They are fixed with the following changes,
please consider applying them wherever they apply cleanly (I have
included the release they first appeared in):

1f1e87b4dc45 ("block: drbd: drbd_nl: Make conversion to 'enum drbd_ret_code' explicit") [5.13]
353f7f3a9dd5 ("drm/amd/display/dc/gpio/gpio_service: Pass around correct dce_{version, environment} types") [5.14]

Since I am here already, please consider applying the following
additional changes where they cleanly apply, as they resolve other
warnings present in x86_64 allmodconfig with clang:

7bf03e7504e4 ("drm/i915: Cast remain to unsigned long in eb_relocate_vma") [5.8]
8a64ef042eab ("nfp: bpf: silence bitwise vs. logical OR warning") [5.15]

If there are any problems or questions, please let me know!

[1]: https://github.com/llvm/llvm-project/commit/882915df61e33f3a2b7f58e52f572717e1c11499

Cheers,
Nathan

             reply	other threads:[~2022-05-10 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 17:49 Nathan Chancellor [this message]
2022-05-12 13:36 ` Warning fixes for clang + x86_64 allmodconfig on 5.10 and 5.4 Greg Kroah-Hartman

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=YnqlnFWCrEz11T5Y@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=llvm@lists.linux.dev \
    --cc=ndesaulniers@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trix@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.