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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a15a54e4-e6f2-4e63-9fc5-141d0e2b010b@kernel.org>
Date: Wed, 21 May 2025 14:19:43 +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>
Subject: Re: [GIT PULL] mux drivers improvements for v6.16

On 21/05/2025 14:14, Greg Kroah-Hartman wrote:
> On Thu, May 15, 2025 at 03:34:51PM +0200, Krzysztof Kozlowski wrote:
>> On 13/05/2025 12:50, Krzysztof Kozlowski wrote:
>>> Hi Greg,
>>>
>>
>>
>> ...
>>
>>>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/mux-drv-6.16
>>>
>>> for you to fetch changes up to 9761037d28327e0d4ee9586a8210ef6462c2c757:
>>>
>>>   mux: adgs1408: fix Wvoid-pointer-to-enum-cast warning (2025-05-08 17:12:08 +0200)
>>>
>>> ----------------------------------------------------------------
>>> Mux drivers for v6.16
>>>
>>> Few cleanups and fixes for the mux drivers:
>>> 1. Simplify with spi_get_device_match_data().
>>> 2. Fix -Wunused-const-variable and -Wvoid-pointer-to-enum-cast warnings.
>>> 3. GPIO mux: add optional regulator for Lenovo T14s laptop headset.
>>> 4. MMIO mux: avoid using syscon's device_node_to_regmap(), due to
>>>    changes in the syscon code.
>>>
>>> ----------------------------------------------------------------
>>> 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/

Best regards,
Krzysztof