From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] uboot-tools: disable pylibfdt
Date: Thu, 2 Nov 2017 22:34:35 +0100 [thread overview]
Message-ID: <20171102223435.6a95fd27@windsurf> (raw)
In-Reply-To: <20171101171849.7957-1-matthew.weber@rockwellcollins.com>
Hello,
On Wed, 1 Nov 2017 12:18:49 -0500, Matt Weber wrote:
> Using concepts from the future upstream fix (post 2017.11),
> which sets up a kconfig variable for pylibfdt and
> conditionally enables the swig wrapper creation (default=n).
> (https://patchwork.ozlabs.org/patch/826742/)
> (https://patchwork.ozlabs.org/patch/826752/)
>
> This does not disable the use of the swig wrapper directly with
> the version of u-boot being used. The uboot package still has
> the BR2_TARGET_UBOOT_NEEDS_PYLIBFDT option to enable this feature.
>
> Fixes (one of many):
> http://autobuild.buildroot.net/results/f9e13caae9b31c9dcde7d24caecc036324f269cc
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
>
> --
> Changes
> v2 -> v3
> - Moved from removing the swig and python to instead following
> the pattern of the future changes captured in this patchset
> to expose it through kconfig.
> (https://lists.denx.de/pipermail/u-boot/2017-October/309560.html)
>
> v1 -> v2
> - Removed all swig and python content from Makefile and noted
> future changes coming upstream in 2017.11
> ---
> .../0004-uboot-tools-disable-pylibfdt.patch | 72 ++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 package/uboot-tools/0004-uboot-tools-disable-pylibfdt.patch
Applied to master, with an improved commit log. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-02 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 17:18 [Buildroot] [PATCH v3] uboot-tools: disable pylibfdt Matt Weber
2017-11-02 18:26 ` Jan Kundrát
2017-11-02 21:34 ` Thomas Petazzoni [this message]
2017-11-16 14:34 ` Peter Korsgaard
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=20171102223435.6a95fd27@windsurf \
--to=thomas.petazzoni@free-electrons.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