[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a4782f3-53d0-7af7-2034-e31879efbc45@foss.st.com>
Date: Tue, 15 Mar 2022 10:02:53 +0100
From: Hugues FRUCHET - FOSS <hugues.fruchet@...s.st.com>
To: Mauro Carvalho Chehab <mchehab@...nel.org>
CC: Alain Volmat <alain.volmat@...s.st.com>,
Niklas Söderlund
<niklas.soderlund+renesas@...natech.se>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Alexey Khoroshilov <khoroshilov@...ras.ru>,
Dillon Min <dillon.minfei@...il.com>,
Dmitriy Ulitin <ulitin@...ras.ru>,
Dmitry Osipenko <digetx@...il.com>,
Eugen Hristev <eugen.hristev@...rochip.com>,
Hans Verkuil <hverkuil-cisco@...all.nl>,
Jacopo Mondi <jacopo@...ndi.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Leon Romanovsky <leon@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Ming Qian <ming.qian@....com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-media@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>
Subject: Re: [PATCH 17/24] media: platform: rename stm32/ to sti/stm32/
Hi Mauro,
sti and stm32 architectures don't have the same maintainers nor same
mailing list as you can see below:
ARM/STM32 ARCHITECTURE
M: Maxime Coquelin <mcoquelin.stm32@...il.com>
M: Alexandre Torgue <alexandre.torgue@...s.st.com>
L: linux-stm32@...md-mailman.stormreply.com (moderated for
non-subscribers)
L: linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
S: Maintained
T: git
git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next
F: arch/arm/boot/dts/stm32*
F: arch/arm/mach-stm32/
F: drivers/clocksource/armv7m_systick.c
N: stm32
N: stm
ARM/STI ARCHITECTURE
M: Patrice Chotard <patrice.chotard@...s.st.com>
L: linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
S: Maintained
W: http://www.stlinux.com
F: Documentation/devicetree/bindings/i2c/i2c-st.txt
F: arch/arm/boot/dts/sti*
F: arch/arm/mach-sti/
F: drivers/ata/ahci_st.c
F: drivers/char/hw_random/st-rng.c
F: drivers/clocksource/arm_global_timer.c
F: drivers/clocksource/clksrc_st_lpc.c
F: drivers/cpufreq/sti-cpufreq.c
F: drivers/dma/st_fdma*
F: drivers/i2c/busses/i2c-st.c
F: drivers/media/platform/sti/c8sectpfe/
F: drivers/media/rc/st_rc.c
F: drivers/mmc/host/sdhci-st.c
F: drivers/phy/st/phy-miphy28lp.c
F: drivers/phy/st/phy-stih407-usb.c
F: drivers/pinctrl/pinctrl-st.c
F: drivers/remoteproc/st_remoteproc.c
F: drivers/remoteproc/st_slim_rproc.c
F: drivers/reset/sti/
F: drivers/rtc/rtc-st-lpc.c
F: drivers/tty/serial/st-asc.c
F: drivers/usb/dwc3/dwc3-st.c
F: drivers/usb/host/ehci-st.c
F: drivers/usb/host/ohci-st.c
F: drivers/watchdog/st_lpc_wdt.c
F: include/linux/remoteproc/st_slim_rproc.h
but anyway, if this is really important for you to have a top folder to
group all ST stuff, we prefer to have "st" prefix than "stm":
> ./drivers/media/platform/st/sti/
> ./drivers/media/platform/st/stm32/
But one more time, our flavour is to stick to:
> ./drivers/media/platform/sti/
> ./drivers/media/platform/stm32/
Best regards,
Hugues.
On 3/14/22 2:10 PM, Mauro Carvalho Chehab wrote:
> Em Mon, 14 Mar 2022 12:34:47 +0100
> Hugues FRUCHET - FOSS <hugues.fruchet@...s.st.com> escreveu:
>
>> Hi Mauro,
>>
>> Ideally we would like to stick to sti/ and stm32/ at same level, as it
>> is done in various other locations:
>>
>> ./Documentation/arm/sti/
>> ./Documentation/arm/stm32/
>>
>> ./arch/arm/mach-sti
>> ./arch/arm/mach-stm32
>>
>> ./drivers/media/cec/platform/sti/
>> ./drivers/media/cec/platform/stm32/
>>
>> ./drivers/gpu/drm/sti/
>> ./drivers/gpu/drm/stm/
>>
>> ./sound/soc/sti/
>> ./sound/soc/stm/
>>
>> Is this possible to keep those media folders as is ?
>
> If we add them under:
> ./drivers/media/platform/stm/sti/
> ./drivers/media/platform/stm/stm32/
>
> They'll both be at the same level.
>
> It has been increasingly hard to maintain media/platform, as the file
> become too big and disorganized. Sorting it per-vendor seems to be the
> best thing, as it will keep things better organized.
>
> As a side effect, with such kind of change, it is now possible to
> have a MAINTAINERS entry that would point to a mailing list and/or
> some SoC maintainers/reviewers that should be c/c to all patches
> affecting drivers/media/platform/<vendor>.
>
> Thanks,
> Mauro
>
Powered by blists - more mailing lists