From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hugues FRUCHET - FOSS <hugues.fruchet@foss.st.com>
Cc: "Alain Volmat" <alain.volmat@foss.st.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Alexey Khoroshilov" <khoroshilov@ispras.ru>,
"Dillon Min" <dillon.minfei@gmail.com>,
"Dmitriy Ulitin" <ulitin@ispras.ru>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Eugen Hristev" <eugen.hristev@microchip.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Ming Qian" <ming.qian@nxp.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 17/24] media: platform: rename stm32/ to sti/stm32/
Date: Wed, 16 Mar 2022 14:28:50 +0100 [thread overview]
Message-ID: <20220316142850.6005b09c@coco.lan> (raw)
In-Reply-To: <8a4782f3-53d0-7af7-2034-e31879efbc45@foss.st.com>
Em Tue, 15 Mar 2022 10:02:53 +0100
Hugues FRUCHET - FOSS <hugues.fruchet@foss.st.com> escreveu:
> 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@gmail.com>
> M: Alexandre Torgue <alexandre.torgue@foss.st.com>
> L: linux-stm32@st-md-mailman.stormreply.com (moderated for
> non-subscribers)
> L: linux-arm-kernel@lists.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@foss.st.com>
> L: linux-arm-kernel@lists.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
Ok.
> 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/
Works for me. Yeah, it is important to have them at the same dir.
After this series, there's a comment on each platform subdir that
tells what vendor is there. That is meant to help selecting the right
drivers with make menuconfig/gconfig/xconfig, and it is reflected at
the .config file. I'm considering to actually add a submenu per vendor.
Ether way, if there's more than one directory per vendor, the "comment"
and/or "menuconfig/if/endif" entries would needed to be moved back to the
drivers/media/platform, making in messier again.
Thanks,
Mauro
next prev parent reply other threads:[~2022-03-16 13:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 10:51 [PATCH 00/24] Organize media platform drivers per manufacturer Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 01/24] media: platform: rename coda/ to chips-media/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 02/24] media: platform: rename marvell-ccic/ to marvell/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 03/24] media: platform: rename meson/ge2d/ to amlogic/meson-ge2d/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 04/24] media: platform: rename mtk-jpeg/ to mediatek/mtk-jpeg/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 05/24] media: platform: rename mtk-mdp/ to mediatek/mtk-mdp/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 06/24] media: platform: rename mtk-vcodec/ to mediatek/mtk-vcodec/ Mauro Carvalho Chehab
2022-03-14 13:09 ` Nicolas Dufresne
2022-03-14 14:37 ` Mauro Carvalho Chehab
2022-03-14 15:02 ` AngeloGioacchino Del Regno
2022-03-14 15:42 ` Mauro Carvalho Chehab
2022-03-14 15:43 ` AngeloGioacchino Del Regno
2022-03-13 10:51 ` [PATCH 07/24] media: platform: rename mtk-vpu/ to mediatek/mtk-vpu/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 08/24] media: platform: rename sunxi/ to allwinner/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 09/24] media: platform: rename tegra/vde/ to nvidia/tegra-vde/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 10/24] media: platform: rename amphion/ to nxp/amphion/ Mauro Carvalho Chehab
2022-03-15 18:26 ` Nicolas Dufresne
2022-03-13 10:51 ` [PATCH 11/24] media: platform: rename exynos4-is/ to samsung/exynos4-is/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 12/24] media: platform: rename exynos-gsc/ to samsung/exynos-gsc/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 13/24] media: platform: rename s3c-camif/ to samsung/s3c-camif/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 14/24] media: platform: rename s5p-g2d/ to samsung/s5p-g2d/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 15/24] media: platform: rename s5p-jpeg/ to samsung/s5p-jpeg/ Mauro Carvalho Chehab
2022-03-14 8:54 ` Andrzej Pietrasiewicz
2022-03-13 10:51 ` [PATCH 16/24] media: platform: rename s5p-mfc/ to samsung/s5p-mfc/ Mauro Carvalho Chehab
2022-03-13 10:51 ` [PATCH 17/24] media: platform: rename stm32/ to sti/stm32/ Mauro Carvalho Chehab
2022-03-14 8:39 ` Alain Volmat
2022-03-14 11:14 ` Mauro Carvalho Chehab
2022-03-14 11:34 ` Hugues FRUCHET - FOSS
2022-03-14 13:10 ` Mauro Carvalho Chehab
2022-03-15 9:02 ` Hugues FRUCHET - FOSS
2022-03-16 13:28 ` Mauro Carvalho Chehab [this message]
2022-03-13 10:51 ` [PATCH 18/24] media: platform: rename am437x/ to ti/am437x/ Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 19/24] media: platform: rename davinci/ to ti/davinci/ Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 20/24] media: platform: rename omap3isp/ to ti/omap3isp/ Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 21/24] media: platform: rename omap/ to ti/omap/ Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 22/24] media: platform: rename ti-vpe/ to ti/vpe/ Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 23/24] media: platform: Create vendor/{Makefile,Kconfig} files Mauro Carvalho Chehab
2022-03-13 10:52 ` [PATCH 24/24] media: platform/*/Kconfig: make menus more uniform Mauro Carvalho Chehab
2022-03-13 11:00 ` [PATCH 00/24] Organize media platform drivers per manufacturer Mauro Carvalho Chehab
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=20220316142850.6005b09c@coco.lan \
--to=mchehab@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=digetx@gmail.com \
--cc=dillon.minfei@gmail.com \
--cc=eugen.hristev@microchip.com \
--cc=hugues.fruchet@foss.st.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=jernej.skrabec@gmail.com \
--cc=khoroshilov@ispras.ru \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ming.qian@nxp.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=ulitin@ispras.ru \
/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