[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB553355D6D5EBC2604E1AD256EE9F0@VI1PR04MB5533.eurprd04.prod.outlook.com>
Date: Mon, 21 Jan 2019 16:16:55 +0000
From: Leonard Crestez <leonard.crestez@....com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Olof Johansson <olof@...om.net>
CC: Rob Herring <robh+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Fabio Estevam <fabio.estevam@....com>,
Mark Rutland <mark.rutland@....com>,
Aisheng Dong <aisheng.dong@....com>,
Leo Li <leoyang.li@....com>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs
On 1/7/2019 9:31 PM, Leonard Crestez wrote:
> The dts makefiles go through a lot of pointless churn when boards are
> added. Many SOCs (such as imx) have very simple naming conventions for
> all boards using a certain chip and board listings can be easily
> collapsed using wildcards.
>
> Add a "wilddt" function and use it for imx6/7/8 and layerscape. This can
> be applied to many other soc families later.
>
> Previously sent as RFC: https://lore.kernel.org/patchwork/patch/1022737/
Any feedback? This should be reviewed by kbuild and arm-soc
I think this is a worthwhile cleanup, are there any corner cases or more
exotic setup I should try in order to validate this series?
--
Regards,
Leonard
Powered by blists - more mailing lists