linux-kernel - Re: linux-next: build failure after merge of the fbdev tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0d4f76d0-9b67-4956-bd13-ce694585a6fd@gmx.de>
Date: Tue, 15 Oct 2024 10:17:15 +0200
From: Helge Deller <deller@....de>
To: Thomas Zimmermann <tzimmermann@...e.de>,
 Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Gonzalo Silvalde Blanco <gonzalo.silvalde@...il.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the fbdev tree

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