From: Nathan Chancellor <nathan@kernel•org>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
clang-built-linux <llvm@lists•linux.dev>,
dri-devel@lists•freedesktop.org, intel-gfx@lists•freedesktop.org,
lkft-triage@lists•linaro.org, Arnd Bergmann <arnd@arndb•de>,
arun.r.murthy@intel•com, Daniel Vetter <daniel@ffwll•ch>,
David Airlie <airlied@gmail•com>
Subject: Re: next: clang: x86_64: /intel_display.c:6012:3: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough]
Date: Wed, 24 May 2023 08:39:18 -0700 [thread overview]
Message-ID: <20230524153918.GA869320@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+G9fYv68V3ewK0Qj-syQj7qX-hQr0H1MFL=QFNuDoE_J2Zu-g@mail.gmail.com>
Hi Naresh,
On Wed, May 24, 2023 at 12:32:24PM +0530, Naresh Kamboju wrote:
> Linux next-20230523 and next-20230524 the x86_64 and i386 builds failed
> with clang.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
>
> make --silent --keep-going \
> --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=x86_64 \
> SRCARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- \
> 'HOSTCC=sccache clang' 'CC=sccache clang' \
> LLVM=1 LLVM_IAS=1
>
> drivers/gpu/drm/i915/display/intel_display.c:6012:3: error:
> unannotated fall-through between switch labels
> [-Werror,-Wimplicit-fallthrough]
> case I915_FORMAT_MOD_X_TILED:
> ^
> drivers/gpu/drm/i915/display/intel_display.c:6012:3: note: insert
> 'break;' to avoid fall-through
> case I915_FORMAT_MOD_X_TILED:
> ^
> break;
> 1 error generated.
Thanks for the report, I have sent
https://lore.kernel.org/20230524-intel_async_flip_check_hw-implicit-fallthrough-v1-1-83de89e376a1@kernel.org/
for this.
Cheers,
Nathan
next prev parent reply other threads:[~2023-05-24 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:02 next: clang: x86_64: /intel_display.c:6012:3: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough] Naresh Kamboju
2023-05-24 15:39 ` Nathan Chancellor [this message]
2023-05-24 15:41 ` Daniel Díaz
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=20230524153918.GA869320@dev-arch.thelio-3990X \
--to=nathan@kernel$(echo .)org \
--cc=airlied@gmail$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=arun.r.murthy@intel$(echo .)com \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=naresh.kamboju@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox