From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: mainline build failure due to f1e4c916f97f ("drm/edid: add EDID block count and size helpers")
Date: Fri, 27 May 2022 10:07:25 +0100 [thread overview]
Message-ID: <YpCUzStDnSgQLNFN@debian> (raw)
Hi All,
The latest mainline kernel branch fails to build for arm spear3xx_defconfig
with the error:
In function 'edid_block_data',
inlined from 'drm_edid_is_valid' at drivers/gpu/drm/drm_edid.c:1904:25:
././include/linux/compiler_types.h:352:45: error: call to '__compiletime_assert_250'
declared with attribute error: BUILD_BUG_ON failed: sizeof(*edid) != EDID_LENGTH
352 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
git bisect pointed to f1e4c916f97f ("drm/edid: add EDID block count and size helpers")
And, reverting it on top of mainline branch has fixed the build failure.
--
Regards
Sudip
next reply other threads:[~2022-05-27 9:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:07 Sudip Mukherjee [this message]
2022-05-27 18:56 ` mainline build failure due to f1e4c916f97f ("drm/edid: add EDID block count and size helpers") Linus Torvalds
2022-05-27 23:40 ` Sudip Mukherjee
2022-05-28 1:04 ` Linus Torvalds
2022-05-28 10:07 ` Sudip Mukherjee
2022-05-28 12:13 ` Sudip Mukherjee
2022-05-28 17:40 ` Linus Torvalds
2022-05-28 18:08 ` Linus Torvalds
2022-05-28 18:58 ` Arnd Bergmann
2022-05-28 20:31 ` Linus Torvalds
2022-05-28 21:08 ` Arnd Bergmann
2022-05-30 9:31 ` Jani Nikula
2022-05-30 9:33 ` Jani Nikula
2022-05-30 12:43 ` Arnd Bergmann
2022-05-30 13:10 ` Jani Nikula
2022-05-30 13:35 ` Arnd Bergmann
2022-05-30 14:08 ` Jani Nikula
2022-05-30 14:26 ` Arnd Bergmann
2022-05-31 6:26 ` Julia Lawall
2022-05-31 8:04 ` Arnd Bergmann
2022-05-31 16:41 ` Linus Torvalds
2022-06-01 22:28 ` Keisuke Nishimura
2022-06-02 1:08 ` Linus Torvalds
2022-06-02 7:38 ` Arnd Bergmann
2022-06-02 11:21 ` Tetsuo Handa
2022-06-02 12:11 ` Arnd Bergmann
2022-06-02 12:19 ` Christoph Hellwig
2022-06-06 10:51 ` Keisuke Nishimura
2022-05-30 16:56 ` Russell King (Oracle)
2022-05-30 16:54 ` Russell King (Oracle)
2022-05-30 16:53 ` Russell King (Oracle)
2022-05-28 20:32 ` Russell King (Oracle)
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=YpCUzStDnSgQLNFN@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).