From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: Build dtb files in all target
Date: Sat, 1 Sep 2012 16:49:22 +0200 [thread overview]
Message-ID: <20120901144922.GA25277@lunn.ch> (raw)
In-Reply-To: <1346303687-7795-1-git-send-email-andrew@lunn.ch>
On Thu, Aug 30, 2012 at 07:14:47AM +0200, Andrew Lunn wrote:
> Tools like kisskb are good at finding build regressions in the kernel
> sources. However, regressions in the DT desscriptions are not found,
> because generally these build systems don't build the DT binary blobs.
>
> Extend the ARM all target to build all enabled DTB files.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> v2: * in the help test
> Only invoke dtbs if CONFIGUSE_OF=y
>
> arch/arm/Makefile | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> index 30eae87..0457ef4 100644
> --- a/arch/arm/Makefile
> +++ b/arch/arm/Makefile
> @@ -268,7 +268,12 @@ else
> KBUILD_IMAGE := zImage
> endif
>
> -all: $(KBUILD_IMAGE)
> +# Build the DT binary blobs if we have OF configured
> +ifeq ($(CONFIG_USE_OF),y)
> +KBUILD_DTBS := dtbs
> +endif
> +
> +all: $(KBUILD_IMAGE) $(KBUILD_DTBS)
>
> boot := arch/arm/boot
>
> @@ -306,7 +311,7 @@ define archhelp
> echo ' uImage - U-Boot wrapped zImage'
> echo ' bootpImage - Combined zImage and initial RAM disk'
> echo ' (supply initrd image via make variable INITRD=<path>)'
> - echo ' dtbs - Build device tree blobs for enabled boards'
> + echo '* dtbs - Build device tree blobs for enabled boards'
> echo ' install - Install uncompressed kernel'
> echo ' zinstall - Install compressed kernel'
> echo ' uinstall - Install U-Boot wrapped compressed kernel'
> --
> 1.7.10.4
>
Hi Folks
Would anybody like to comment about the patch itself?
Assuming the patch is acceptable, through which maintainers tree
should it be submitted?
Thanks
Andrew
next prev parent reply other threads:[~2012-09-01 14:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 5:14 [PATCH v2] ARM: Build dtb files in all target Andrew Lunn
2012-08-30 16:52 ` Jason Cooper
2012-08-30 17:23 ` Russell King - ARM Linux
2012-08-30 18:37 ` Jason Cooper
2012-08-30 19:14 ` Russell King - ARM Linux
2012-08-30 19:40 ` Jason Cooper
2012-08-31 21:11 ` Ben Hutchings
2012-08-31 22:32 ` Russell King - ARM Linux
2012-09-01 14:20 ` Ben Hutchings
2012-09-01 15:25 ` Russell King - ARM Linux
2012-09-01 16:32 ` Jonathan Nieder
2012-09-01 18:22 ` Russell King - ARM Linux
2012-09-01 18:38 ` Jonathan Nieder
2012-09-01 20:11 ` Russell King - ARM Linux
2012-09-02 6:30 ` When to cc stable@vger.kernel.org (Re: [PATCH v2] ARM: Build dtb files in all target) Jonathan Nieder
2012-09-02 13:54 ` [PATCH v2] ARM: Build dtb files in all target Ben Hutchings
2012-09-02 17:04 ` Russell King - ARM Linux
2012-09-02 17:26 ` Ben Hutchings
2012-09-02 18:05 ` Russell King - ARM Linux
2012-09-02 19:14 ` Uwe Kleine-König
2012-09-02 23:58 ` Greg KH
2012-08-30 18:03 ` Greg KH
2012-09-01 14:49 ` Andrew Lunn [this message]
2012-09-03 12:21 ` Dave Martin
2012-09-03 19:55 ` Jason Cooper
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=20120901144922.GA25277@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
/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).