From: <Nicolas.Ferre@microchip.com>
To: <robh@kernel.org>, <arm@kernel.org>
Cc: andrew@lunn.ch, alexandre.belloni@bootlin.com, tony@atomide.com,
linus.walleij@linaro.org, liviu.dudau@arm.com,
yamada.masahiro@socionext.com, thierry.reding@gmail.com,
f.fainelli@gmail.com, khilman@kernel.org,
gregory.clement@bootlin.com, michal.simek@xilinx.com,
krzk@kernel.org, Ludovic.Desroches@microchip.com, joel@jms.id.au,
andy.gross@linaro.org, devicetree@vger.kernel.org,
jason@lakedaemon.net, horms@verge.net.au,
linux-arm-kernel@lists.infradead.org, mcoquelin.stm32@gmail.com,
shawnguo@kernel.org, afaerber@suse.de, daniel@zonque.org
Subject: Re: Moving ARM dts files
Date: Wed, 5 Dec 2018 08:13:37 +0000 [thread overview]
Message-ID: <392c9399-83c8-a74a-a849-748225802851@microchip.com> (raw)
In-Reply-To: <20181204183649.GA5716@bogus>
On 04/12/2018 at 19:36, Rob Herring wrote:
> Olof, Arnd,
>
> I've put together a script to move the dts files and update the
> makefiles. It doesn't handle files not following a common prefix which
> isn't many and some includes within the dts files will need some fixups
> by hand.
>
> MAINTAINERS will also need updating.
>
> A few questions:
>
> Do we want to move absolutely everything to subdirs? There's quite a
> few platforms with only 1-2 platforms. I haven't added these to the
> list yet, but can.
>
> Do any vendors need another level of directories? davinci, omap, nspire,
> etc. for TI for example.
>
> What to do with armv7m.dtsi? I guess it should remain and we just fixup
> the include. There may be a few other cross vendor things.
>
>
> Sub-arch maintainers,
> 'vendor_map' below is the mapping of file prefix to new subdirectory
> (the SoC vendor prefix). Please comment if there are any issues.
It'll certainly break some of our scripts (CI, building scripts, overlay
makefiles, etc.). We already experienced it when adding the "dts"
directory. But if it's needed...
> 8<-----------------------------------------------------------
> #!/usr/bin/env python3
>
> import os
> import re
> from git import Git
> import glob
>
> vendor_map = {
[..]
> 'integ' : 'arm',
> 've' : 'arm',
> 'aspeed' : 'aspeed',
> 'at91' : 'atmel',
As it's a new directory, what about creating a "microchip" one as it's
our vendor's name now.
> 'sama' : 'atmel',
If desired, you can extend to sama5d for the current files.
Adding the entry 'sam9' : "microchip", can be future proof...
Best regards,
--
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-05 8:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:36 Moving ARM dts files Rob Herring
2018-12-04 18:47 ` Alexandre Belloni
2018-12-04 19:09 ` Rob Herring
2018-12-04 22:21 ` Simon Horman
2018-12-05 1:22 ` Andreas Färber
2018-12-05 4:17 ` Rob Herring
2018-12-05 17:33 ` Tom Rini
2018-12-06 13:32 ` Andreas Färber
2018-12-06 19:06 ` Rob Herring
2018-12-06 20:06 ` Mark Brown
2018-12-06 20:49 ` Olof Johansson
2018-12-07 14:57 ` Rob Herring
2018-12-07 15:16 ` Mark Brown
2018-12-07 15:29 ` Rob Herring
2018-12-06 20:14 ` Tom Rini
2018-12-05 4:18 ` Masahiro Yamada
2018-12-05 9:48 ` Michal Simek
2018-12-05 6:02 ` Jisheng Zhang
2018-12-05 8:19 ` Linus Walleij
2018-12-05 8:34 ` Jisheng Zhang
2018-12-05 9:04 ` Linus Walleij
2018-12-05 15:01 ` Rob Herring
2018-12-05 21:03 ` Linus Walleij
2018-12-06 13:39 ` Uwe Kleine-König
2018-12-06 13:58 ` Rob Herring
2018-12-06 14:05 ` Alexandre Belloni
2018-12-06 14:30 ` Linus Walleij
2018-12-06 16:57 ` Rob Herring
2018-12-06 22:12 ` Linus Walleij
2018-12-07 23:35 ` Tony Lindgren
2018-12-05 8:13 ` Nicolas.Ferre [this message]
2018-12-05 15:14 ` Neil Armstrong
2018-12-05 17:36 ` Li Yang
2018-12-07 22:33 ` Rob Herring
2018-12-08 9:25 ` Krzysztof Kozlowski
2018-12-08 22:40 ` Linus Walleij
2018-12-11 15:58 ` Olof Johansson
2018-12-08 10:07 ` Ian Campbell
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=392c9399-83c8-a74a-a849-748225802851@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=afaerber@suse.de \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=joel@jms.id.au \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).