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: <20220314141008.13e32acd@coco.lan>
Date:   Mon, 14 Mar 2022 14:10:08 +0100
From:   Mauro Carvalho Chehab <mchehab@...nel.org>
To:     Hugues FRUCHET - FOSS <hugues.fruchet@...s.st.com>
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/

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ