linux-kernel - Re: [GIT PULL] mux drivers improvements for v6.16

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: <a2a619f9-d6ca-419d-af11-e41b6ae59a48@kernel.org>
Date: Wed, 21 May 2025 17:25:14 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 linux-kernel@...r.kernel.org, Peter Rosin <peda@...ntia.se>,
 Mark Brown <broonie@...nel.org>
Subject: Re: [GIT PULL] mux drivers improvements for v6.16

On 21/05/2025 14:19, Krzysztof Kozlowski wrote:
>>>>
>>>> ----------------------------------------------------------------
>>>> Andrew Davis (1):
>>>>       mux: mmio: Do not use syscon helper to build regmap
>>> I received LKP build error report for some specific configuration:
>>> https://lore.kernel.org/oe-kbuild-all/202505150312.dYbBqUhG-lkp@intel.com/
>>>
>>> I will send a follow up fix for that and then later updated pull
>>> request, if you do not pull it till that time.
>>
>> I've taken this now, do you have a fix somewhere?
> Fix is being discussed on the lists, because it exposes Kconfig circular
> dependency:
> 
> 1. The actual fix which also tries to break circular dependency:
> https://lore.kernel.org/all/20250515140555.325601-2-krzysztof.kozlowski@linaro.org/
> 
> 2. A better way to break circular dependency:
> https://lore.kernel.org/all/20250516141722.13772-1-afd@ti.com/

+Cc Mark Brown,

Above circular-dependency-break (2) was applied by Mark for v6.16-rc1:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=for-6.16&id=c5a219395b4e6312102a505bfe73aac8f8bada8c

This means that my fix for LKP build error, should come after. My
proposal is to live with the LKP build error till v6.16-rc1 and then
apply my fix. I just sent v2 of my fix for LKP build error:
https://lore.kernel.org/r/20250521152354.92720-2-krzysztof.kozlowski@linaro.org/

Best regards,
Krzysztof