Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/linux: fix custom dts files handling
Date: Sat, 31 Mar 2018 22:59:20 +0200	[thread overview]
Message-ID: <87370gt107.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180313180006.5364-1-rafal.susz@gmail.com> (Rafal Susz's message of "Tue, 13 Mar 2018 19:00:05 +0100")

>>>>> "Rafal" == Rafal Susz <rafal.susz@gmail.com> writes:

 > Custom dts files are still conditionally copied based on non existing
 > boolean. So it is currently not possible to use custom dts file(s) at all.

 > List of dts files is now iterated and files are copied into dedicated kernel arch dir.

 > Signed-off-by: Rafal Susz <rafal.susz@gmail.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-03-31 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 21:35 [Buildroot] [PATCH 1/1] package/linux: fix custom dts files handling Rafal Susz
2018-03-13 11:32 ` Rafal Susz
2018-03-13 11:49   ` Baruch Siach
2018-03-13 12:31     ` Rafał Susz
2018-03-13 12:45       ` Baruch Siach
2018-03-13 14:26   ` Rafal Susz
2018-03-13 17:21     ` Yann E. MORIN
2018-03-13 18:00     ` [Buildroot] [PATCH 1/2] " Rafal Susz
2018-03-13 18:00       ` [Buildroot] [PATCH 2/2] configs/s6lx9_microboard_defconfig: purge custom dts boolean Rafal Susz
2018-03-31 20:59         ` Peter Korsgaard
2018-03-14 15:20       ` [Buildroot] [PATCH 1/2] package/linux: fix custom dts files handling Jan Kundrát
2018-03-31 20:59       ` Peter Korsgaard [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=87370gt107.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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