From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Ioana Ciornei <ioana.ciornei@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stuart Yoder <stuyoder@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Maintenance path for the fsl-mc bus
Date: Tue, 18 Mar 2025 14:46:55 +0100 [thread overview]
Message-ID: <1d822960-85a7-42b3-88cf-9d3dbc75a831@csgroup.eu> (raw)
In-Reply-To: <2xzljdzktgpsyag5jhfwbxc2sroaacljecsq36hlxefu6jnz6g@zlorxu7niqnq>
Hi Ioana,
Le 18/03/2025 à 11:40, Ioana Ciornei a écrit :
> [Vous ne recevez pas souvent de courriers de ioana.ciornei@nxp.com. D?couvrez pourquoi ceci est important ? https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi,
>
> As highlighted by the discussion in the following thread, the
> maintenance path for the fsl-mc bus is not clear.
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Flinux-arm-kernel%2FZ9Lj9_yM1EK5pKee%40gallifrey&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C00bf096aa0fe40f9d8e908dd66094d7d%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638778912314503921%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2F%2B%2FXzSQ9VUY81xPbjB8%2F0vIIF9ChaTRXupWd59%2Fvfco%3D&reserved=0
>
> 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?
Yes its fine for me to take it via my soc fsl subtree unless Arnd tells
different. But be aware that it will be purely administrative. I will
have no mean to check whether any changes are actually working properly.
In that case please add the following entry in MAINTAINERS:
L: linuxppc-dev@lists.ozlabs.org
>
> 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
next prev parent reply other threads:[~2025-03-18 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:40 Ioana Ciornei
2025-03-18 13:46 ` Christophe Leroy [this message]
2025-03-18 14:22 ` Ioana Ciornei
2025-03-18 14:31 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d822960-85a7-42b3-88cf-9d3dbc75a831@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stuyoder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®