From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the drm-msm tree
Date: Tue, 10 Oct 2023 12:54:51 +1100 [thread overview]
Message-ID: <20231010125451.533d0dbc@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
Hi all,
After merging the drm-msm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/msm/msm_drv.c:59:1: error: data definition has no type or storage class [-Werror]
59 | DECLARE_FAULT_ATTR(fail_gem_alloc);
| ^~~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/msm_drv.c:59:1: error: type defaults to 'int' in declaration of 'DECLARE_FAULT_ATTR' [-Werror=implicit-int]
drivers/gpu/drm/msm/msm_drv.c:59:1: error: parameter names (without types) in function declaration [-Werror]
drivers/gpu/drm/msm/msm_drv.c:60:1: error: data definition has no type or storage class [-Werror]
60 | DECLARE_FAULT_ATTR(fail_gem_iova);
| ^~~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/msm_drv.c:60:1: error: type defaults to 'int' in declaration of 'DECLARE_FAULT_ATTR' [-Werror=implicit-int]
drivers/gpu/drm/msm/msm_drv.c:60:1: error: parameter names (without types) in function declaration [-Werror]
drivers/gpu/drm/msm/msm_drv.c: In function 'msm_ioctl_gem_new':
drivers/gpu/drm/msm/msm_drv.c:454:13: error: implicit declaration of function 'should_fail' [-Werror=implicit-function-declaration]
454 | if (should_fail(&fail_gem_alloc, args->size))
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
Presumably caused by commit
506efcba3129 ("drm/msm: carve out KMS code from msm_drv.c")
I have used the drm-msm tree from next-20231009 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-10 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 1:54 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 0:59 linux-next: build failure after merge of the drm-msm tree Stephen Rothwell
2022-05-05 1:48 Stephen Rothwell
2022-05-05 1:43 Stephen Rothwell
2021-07-29 11:28 Mark Brown
2021-06-18 2:42 Stephen Rothwell
2021-06-18 2:50 ` Stephen Rothwell
2021-06-23 1:02 ` Stephen Rothwell
2018-10-05 1:37 Stephen Rothwell
2018-07-23 4:50 Stephen Rothwell
2018-07-25 12:08 ` Rob Clark
2018-06-04 3:20 Stephen Rothwell
2016-07-11 3:20 Stephen Rothwell
2015-12-15 1:27 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=20231010125451.533d0dbc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox