linux-kernel - Re: linux-next: build failure after merge of the tty 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: <b6c4703f-7cea-4253-bfe0-3451b3f6671e@genexis.eu>
Date: Sun, 9 Feb 2025 22:13:29 +0100
From: Benjamin Larsson <benjamin.larsson@...exis.eu>
To: Greg KH <greg@...ah.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
 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 tty tree

On 06/02/2025 09:14, Greg KH wrote:

[...]

>>>
>> COMPILE_TEST seems to be the cause for this.
>>
>> +config SERIAL_8250_AIROHA
>> +     tristate "Airoha UART support"
>> +     depends on (ARCH_AIROHA || COMPILE_TEST) && OF && SERIAL_8250
>>
>>
>> Should I send a patch removing this?
> 
> No, you should allow COMPILE_TEST to build the code, right?  Odd that I
> can't build it here for some reason, I guess I need to enable OF on my
> test builds...
> 
> thanks,
> 
> greg k-h

Hi, I confirm the build error and I tried to properly add support for 
COMPILE_TEST to the code. I did not succeed with that and only got into 
kernel configurations that broke the compilation in non trivial ways.

While it obviously is not impossible to add support I did not like the 
path it was going. Thus I opted for the solution of least complexity and 
removed the COMPILE_TEST option.

A v4 of the patch has been posted.

MvH
Benjamin Larsson