From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Clark <robdclark@gmail•com>, Sean Paul <seanpaul@chromium•org>
Cc: Jessica Zhang <quic_jesszhan@quicinc•com>,
Rob Clark <robdclark@chromium•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-msm tree
Date: Fri, 7 Mar 2025 13:02:38 +1100 [thread overview]
Message-ID: <20250307130238.6d04e6cb@canb.auug.org.au> (raw)
In-Reply-To: <20250307123645.07564e19@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
Hi all,
On Fri, 7 Mar 2025 12:36:45 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the drm-msm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:235:18: warning: 'wb2_formats_rgb' defined but not used [-Wunused-const-variable=]
> 235 | static const u32 wb2_formats_rgb[] = {
> | ^~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 69d02730431e ("drm/msm/dpu: Support YUV formats on writeback for DPU 5.x+")
This became a build failure in the x86_64 allmodconfig build, so I have
used the drm-msm tree from next-20250306 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-07 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 1:36 linux-next: build warning after merge of the drm-msm tree Stephen Rothwell
2025-03-07 2:02 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 4:44 Stephen Rothwell
2025-08-05 3:36 ` Stephen Rothwell
2020-09-21 3:16 Stephen Rothwell
2020-09-14 2:10 Stephen Rothwell
2020-09-17 7:58 ` Stephen Rothwell
2017-11-01 3:46 Stephen Rothwell
2017-11-01 15:19 ` Rob Clark
2017-08-03 3:12 Stephen Rothwell
2017-08-03 3:09 Stephen Rothwell
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=20250307130238.6d04e6cb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=quic_jesszhan@quicinc$(echo .)com \
--cc=robdclark@chromium$(echo .)org \
--cc=robdclark@gmail$(echo .)com \
--cc=seanpaul@chromium$(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