linux-kernel - Maintenance path for the fsl-mc bus

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

Message-ID: <2xzljdzktgpsyag5jhfwbxc2sroaacljecsq36hlxefu6jnz6g@zlorxu7niqnq>
Date: Tue, 18 Mar 2025 12:40:25 +0200
From: Ioana Ciornei <ioana.ciornei@....com>
To: Christophe Leroy <christophe.leroy@...roup.eu>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Stuart Yoder <stuyoder@...il.com>, Arnd Bergmann <arnd@...db.de>
Cc: linux-kernel@...r.kernel.org
Subject: Maintenance path for the fsl-mc bus

Hi,

As highlighted by the discussion in the following thread, the
maintenance path for the fsl-mc bus is not clear.

https://lore.kernel.org/linux-arm-kernel/Z9Lj9_yM1EK5pKee@gallifrey

The fsl-mc bus driver was first added to drivers/staging and because of
that, Greg was to one to pick up patches through his tree. Once it was
moved to drivers/bus/fsl-mc, patches on this driver were picked either
by Greg or by the Freescale SOC maintainer at that time - Li Yang.

Conceptually speaking, the fsl-mc bus driver is contributing to the same
infrastructure level as the SoC drivers maintained now by Christophe.

Christophe, would you be open to pick up patches for this bus driver
through your tree?

As a side note, I know that the MAINTAINERS entry for this driver is not
up to date - Laurentiu's email bounces. I will send a patch updating it
after it's clear to whom I should send it.

Thanks,
Ioana