From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: at91: move dts to subdir
Date: Wed, 10 Apr 2013 19:44:25 +0200 [thread overview]
Message-ID: <20130410174425.GA20693@game.jcrosoft.org> (raw)
In-Reply-To: <5165A3BE.4070001@wwwdotorg.org>
On 11:39 Wed 10 Apr , Stephen Warren wrote:
> On 04/10/2013 03:17 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>
> A patch description might be nice.
>
> This seems like a nice cleanup to keep the dts directory organized.
yeah I was really not a fan on the prefix stuff
> However, it does mean that the *.dtb files get moved again. I know that
> when they moved from boot/ to boot/dts/ in 3.9 (or 3.8?) there were some
> complaints that this made it difficult to write scripts that find the
> built DTB and copy it somewhere. This change would cause the exact same
> problem again.
yes this will move the dtb location to the subdir
>
> Perhaps it's time to create an install_dtbs target to solve this problem?
I think about it too but was not sure if it will be usefull
as you may end with all the mach-xxx dtb generated and on embedded system you
do not want all of them on contrary on Ubuntu & co
I was also think to make it more generic so move the code to Kbuild
so any arch can use it
next prev parent reply other threads:[~2013-04-10 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 9:17 [PATCH 1/2] ARM: boot/dts/Makefile: drop '\' Jean-Christophe PLAGNIOL-VILLARD
2013-04-10 9:17 ` [PATCH 2/2] ARM: at91: move dts to subdir Jean-Christophe PLAGNIOL-VILLARD
2013-04-10 17:39 ` Stephen Warren
2013-04-10 17:44 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-04-10 17:47 ` Olof Johansson
2013-04-10 17:35 ` [PATCH 1/2] ARM: boot/dts/Makefile: drop '\' Stephen Warren
2013-04-10 17:48 ` 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=20130410174425.GA20693@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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).