From: Helge Deller <deller@gmx•de>
To: Thomas Zimmermann <tzimmermann@suse•de>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Gonzalo Silvalde Blanco <gonzalo.silvalde@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the fbdev tree
Date: Tue, 15 Oct 2024 10:17:15 +0200 [thread overview]
Message-ID: <0d4f76d0-9b67-4956-bd13-ce694585a6fd@gmx.de> (raw)
In-Reply-To: <7df614b3-4b6c-490a-b64b-ceabf7d2d290@suse.de>
On 10/15/24 09:15, Thomas Zimmermann wrote:
> Hi
>
> Am 15.10.24 um 03:01 schrieb Stephen Rothwell:
>> Hi all,
>>
>> After merging the fbdev tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> drivers/video/fbdev/sstfb.c: In function 'sstfb_probe':
>> drivers/video/fbdev/sstfb.c:1439:2: error: invalid preprocessing directive #fdef; did you mean #ifdef?
>> 1439 | #fdef CONFIG_FB_DEVICE
>> | ^~~~
>> | ifdef
>> drivers/video/fbdev/sstfb.c:1442:2: error: #endif without #if
>> 1442 | #endif
>> | ^~~~~
>>
>> Caused by commit
>>
>> 7c0510bb3452 ("fbdev: sstfb: Make CONFIG_FB_DEVICE optional")
>>
>> I have used the fbdev tree from next-20241014 for today.
>
> Thanks for reporting. While it has my r-b, it wasn't supposed to be merged yet. I sent out a fix to address the remaining problems. See
>
> https://lore.kernel.org/linux-fbdev/20241015071029.25639-1-tzimmermann@suse.de/T/#u
Thanks Thomas and Stephen!
I've merged Thomas changes into one patch and pushed a new version.
The issue should be resolved now.
Helge
next prev parent reply other threads:[~2024-10-15 8:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 1:01 linux-next: build failure after merge of the fbdev tree Stephen Rothwell
2024-10-15 7:15 ` Thomas Zimmermann
2024-10-15 8:17 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-08 23:44 Mark Brown
2022-02-16 0:29 Stephen Rothwell
2022-02-16 7:16 ` 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=0d4f76d0-9b67-4956-bd13-ce694585a6fd@gmx.de \
--to=deller@gmx$(echo .)de \
--cc=gonzalo.silvalde@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tzimmermann@suse$(echo .)de \
/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