From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Helge Deller <deller@gmx.de>
Cc: Yong Wu <yong.wu@mediatek.com>,
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 fbdev tree
Date: Wed, 16 Feb 2022 11:29:34 +1100 [thread overview]
Message-ID: <20220216112934.108a27ad@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Hi all,
After merging the fbdev tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/video/fbdev/omap2/omapfb/dss/dss.c: In function 'dss_add_child_component':
drivers/video/fbdev/omap2/omapfb/dss/dss.c:1209:49: error: 'component_compare_dev' undeclared (first use in this function); did you mean 'component_master_del'?
1209 | component_match_add(dev->parent, match, component_compare_dev, dev);
| ^~~~~~~~~~~~~~~~~~~~~
| component_master_del
Caused by commit
61038027aa13 ("video: fbdev: omapfb: Make use of the helper component_compare_dev")
I have used the fbdev tree from next-20220215 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-16 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 0:29 Stephen Rothwell [this message]
2022-02-16 7:16 ` linux-next: build failure after merge of the fbdev tree Helge Deller
-- strict thread matches above, loose matches on Subject: below --
2026-02-08 23:44 Mark Brown
2024-10-15 1:01 Stephen Rothwell
2024-10-15 7:15 ` Thomas Zimmermann
2024-10-15 8:17 ` Helge Deller
2019-06-20 1:41 Stephen Rothwell
2019-06-24 1:45 ` Stephen Rothwell
2019-06-24 4:15 ` Stephen Rothwell
2018-06-29 1:07 Stephen Rothwell
2018-06-29 9:32 ` Hans de Goede
2011-04-07 2:48 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=20220216112934.108a27ad@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=yong.wu@mediatek.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