[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b6317087abfa81b37b0ac800b192f8e32786ce9a.camel@nxp.com>
Date: Wed, 30 Jan 2019 13:16:52 +0000
From: Leonard Crestez <leonard.crestez@....com>
To: "olof@...om.net" <olof@...om.net>,
"yamada.masahiro@...ionext.com" <yamada.masahiro@...ionext.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>
CC: Aisheng Dong <aisheng.dong@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Leo Li <leoyang.li@....com>,
Fabio Estevam <fabio.estevam@....com>,
"michal.lkml@...kovi.net" <michal.lkml@...kovi.net>,
"mark.rutland@....com" <mark.rutland@....com>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs
On Fri, 2019-01-25 at 01:03 +0900, Masahiro Yamada wrote:
> On Tue, Jan 22, 2019 at 1:17 AM Leonard Crestez <leonard.crestez@....com> wrote:
> >
> > 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.
> >
> > Any feedback? This should be reviewed by kbuild and arm-soc
>
> Personally, I prefer explicit listing
> because I can browse the Makefile to get a quick idea
> of which boards are compiled.
Or you can just ls soc-*.dts?
> I like this to be consistent.
> - Exploit wildcard for all platforms
> - Do not do this at all
>
> But, I am pessimistic about the former
> when I look at AT91 platform.
I can try to resend in a form that uses a wildcard for most platforms
but skips those with very few SOCs or confusing conventions (like
at91).
--
Regards,
Leonard
Powered by blists - more mailing lists