devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	nunojpg@gmail.com
Subject: Re: [PATCH] builddeb: Fix inclusion of dtbs in debian package
Date: Fri, 9 Nov 2018 00:26:07 +0900	[thread overview]
Message-ID: <CAK7LNATcs4bZv6Q1BEkb+V_SdiBek-fawO1RWKuh68uPN7ymUA@mail.gmail.com> (raw)
In-Reply-To: <20181107143646.27675-1-robh@kernel.org>

On Wed, Nov 7, 2018 at 11:37 PM Rob Herring <robh@kernel.org> wrote:
>
> Commit 37c8a5fafa3b ("kbuild: consolidate Devicetree dtb build rules")
> moved the location of 'dtbs_install' target which caused dtbs to not be
> installed when building debian package with 'bindeb-pkg' target. Update
> the builddeb script to use the same logic that determines if there's a
> 'dtbs_install' target which is presence of the arch dts directory. Also,
> use CONFIG_OF_EARLY_FLATTREE instead of CONFIG_OF as that's a better
> indication of whether we are building dtbs.
>
> This commit will also have the side effect of installing dtbs on any
> arch that has dts files. Previously, it was dependent on whether the
> arch defined 'dtbs_install'.
>
> Fixes: 37c8a5fafa3b ("kbuild: consolidate Devicetree dtb build rules")
> Reported-by: Nuno Gonçalves <nunojpg@gmail.com>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Michal Marek <michal.lkml@markovi.net>
> Cc: linux-kbuild@vger.kernel.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---

Applied to linux-kbuild/fixes.
Thanks!


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2018-11-08 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 14:36 [PATCH] builddeb: Fix inclusion of dtbs in debian package Rob Herring
2018-11-08 15:26 ` Masahiro Yamada [this message]

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=CAK7LNATcs4bZv6Q1BEkb+V_SdiBek-fawO1RWKuh68uPN7ymUA@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nunojpg@gmail.com \
    --cc=robh@kernel.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).