From: Leonard Crestez <leonard.crestez@nxp.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Shawn Guo <shawnguo@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
Fabio Estevam <fabio.estevam@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>, Leo Li <leoyang.li@nxp.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs
Date: Mon, 7 Jan 2019 19:31:25 +0000 [thread overview]
Message-ID: <cover.1546888138.git.leonard.crestez@nxp.com> (raw)
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/
Changes since RFC:
* Split into 3-part series
* Move the wilddt to Kbuild.include so that it's available everywhere
* Use $(srctree)/$(src) instead of $(dtstree)
* Also use wilddt in arm64/boot/dts/freescale
Series is against next-20190107, conflicts are to be expected as board
list keeps changing.
Leonard Crestez (3):
kbuild: Add wilddt function
ARM: dts: imx: Use wilddt function
arm64: dts: freescale: Use wilddt function
arch/arm/boot/dts/Makefile | 201 ++-----------------------
arch/arm64/boot/dts/freescale/Makefile | 25 +--
scripts/Kbuild.include | 6 +
3 files changed, 21 insertions(+), 211 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Shawn Guo <shawnguo@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Michal Marek <michal.lkml@markovi.net>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs
Date: Mon, 7 Jan 2019 19:31:25 +0000 [thread overview]
Message-ID: <cover.1546888138.git.leonard.crestez@nxp.com> (raw)
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/
Changes since RFC:
* Split into 3-part series
* Move the wilddt to Kbuild.include so that it's available everywhere
* Use $(srctree)/$(src) instead of $(dtstree)
* Also use wilddt in arm64/boot/dts/freescale
Series is against next-20190107, conflicts are to be expected as board
list keeps changing.
Leonard Crestez (3):
kbuild: Add wilddt function
ARM: dts: imx: Use wilddt function
arm64: dts: freescale: Use wilddt function
arch/arm/boot/dts/Makefile | 201 ++-----------------------
arch/arm64/boot/dts/freescale/Makefile | 25 +--
scripts/Kbuild.include | 6 +
3 files changed, 21 insertions(+), 211 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-01-07 19:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:31 Leonard Crestez [this message]
2019-01-07 19:31 ` [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs Leonard Crestez
2019-01-07 19:31 ` [PATCH 1/3] kbuild: Add wilddt function Leonard Crestez
2019-01-07 19:31 ` Leonard Crestez
2019-01-07 19:31 ` [PATCH 2/3] ARM: dts: imx: Use " Leonard Crestez
2019-01-07 19:31 ` Leonard Crestez
2019-01-07 19:31 ` [PATCH 3/3] arm64: dts: freescale: " Leonard Crestez
2019-01-07 19:31 ` Leonard Crestez
2019-01-21 16:16 ` [PATCH 0/3] kbuild: Add wilddt function instead of listing dtbs Leonard Crestez
2019-01-21 16:16 ` Leonard Crestez
2019-01-21 16:16 ` Leonard Crestez
2019-01-24 16:03 ` Masahiro Yamada
2019-01-24 16:03 ` Masahiro Yamada
2019-01-30 13:16 ` Leonard Crestez
2019-01-30 13:16 ` Leonard Crestez
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=cover.1546888138.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.lkml@markovi.net \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.