From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: remove generated .dtb files on clean
Date: Wed, 30 Jan 2013 11:59:49 +0530 [thread overview]
Message-ID: <5108BDDD.60307@ti.com> (raw)
In-Reply-To: <1358890049-26981-1-git-send-email-nm@ti.com>
Looping RMK, Arnd
On Wednesday 23 January 2013 02:57 AM, Nishanth Menon wrote:
> commit 5f300acd8ae9f3d4585154370012ffc5c665330f
> (ARM: 7152/1: distclean: Remove generated .dtb files)
> ensured that dtbs were cleaned up when they were in
> arch/arm/boot.
> However, with the following commit:
> commit 499cd8298628eeabf0eb5eb6525d4faa0eec80d8
> (ARM: dt: change .dtb build rules to build in dts directory)
>
> make clean now leaves dtbs in arch/arm/boot/dts/
> untouched. Include dts directory so that clean-files rule
> from arch/arm/boot/dts/Makefile is invoked when make
> clean is done.
>
> Cc: Dirk Behme <dirk.behme@de.bosch.com>
> CC: Grant Likely <grant.likely@secretlab.ca>
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> arch/arm/boot/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
> index abfce28..3837f97 100644
> --- a/arch/arm/boot/Makefile
> +++ b/arch/arm/boot/Makefile
> @@ -115,4 +115,4 @@ i:
> $(CONFIG_SHELL) $(srctree)/$(src)/install.sh $(KERNELRELEASE) \
> $(obj)/Image System.map "$(INSTALL_PATH)"
>
> -subdir- := bootp compressed
> +subdir- := bootp compressed dts
>
Seems to be the valid fix for me.
Regards,
Santosh
next prev parent reply other threads:[~2013-01-30 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 21:27 [PATCH] ARM: dts: remove generated .dtb files on clean Nishanth Menon
2013-01-30 6:29 ` Santosh Shilimkar [this message]
2013-03-01 1:35 ` Nishanth Menon
2013-03-01 1:47 ` Olof Johansson
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=5108BDDD.60307@ti.com \
--to=santosh.shilimkar@ti.com \
--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).