From: Mark Brown <broonie@kernel•org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Maxime Ripard <mripard@kernel•org>
Subject: linux-next: build failure after merge of the drm-msm-lumag tree
Date: Mon, 24 Jun 2024 17:20:05 +0100 [thread overview]
Message-ID: <ZnmctV78elxIFtCV@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
Hi all,
After merging the drm-msm-lumag tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
ERROR: modpost: too long symbol "drm_atomic_helper_connector_hdmi_disable_audio_infoframe" [drivers/gpu/drm/msm/msm.ko]
Caused by commit
000d1940c90984 ("drm/connector: hdmi: allow disabling Audio Infoframe")
I used the version from 20240621 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-06-24 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:20 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 7:07 linux-next: build failure after merge of the drm-msm-lumag tree Stephen Rothwell
2023-05-22 7:15 ` Dmitry Baryshkov
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=ZnmctV78elxIFtCV@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mripard@kernel$(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