From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] android-tools: upport char, block, fifo, socket devices
Date: Fri, 1 Dec 2017 13:55:28 +0100 [thread overview]
Message-ID: <20171201135528.16e0c342@windsurf.lan> (raw)
In-Reply-To: <20171130205631.93251-2-ek9852@gmail.com>
Hello,
Thanks for your contributions! See below for a few comments/questions.
On Thu, 30 Nov 2017 12:56:31 -0800, Keith Mok wrote:
> Pick changes from openwrt to enable support of special
> device for make_ext4fs
Missing Signed-off-by line.
> ---
> ...ment-support-for-block-and-char-dev-nodes.patch | 109 +++++++++++++++++++++
> 1 file changed, 109 insertions(+)
> create mode 100644 package/android-tools/0009-PATCH-Implement-support-for-block-and-char-dev-nodes.patch
>
> diff --git a/package/android-tools/0009-PATCH-Implement-support-for-block-and-char-dev-nodes.patch b/package/android-tools/0009-PATCH-Implement-support-for-block-and-char-dev-nodes.patch
> new file mode 100644
> index 0000000..e86d9c6
> --- /dev/null
> +++ b/package/android-tools/0009-PATCH-Implement-support-for-block-and-char-dev-nodes.patch
> @@ -0,0 +1,109 @@
> +From 3258b175c3ea1f76823c6b69b5036ac7efb5599d Mon Sep 17 00:00:00 2001
> +From: Jo-Philipp Wich <jow@openwrt.org>
> +Date: Thu, 30 Nov 2017 10:10:24 -0800
> +Subject: [PATCH] [PATCH] Implement support for block and char dev nodes, fifos
> + and sockets.
> +
> +Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
> +Signed-off-by: Keith Mok <ek9852@gmail.com>
This really is a feature patch, and we don't like to take features
patches in Buildroot (unlike OpenWRT). Indeed, those are often a pain
to maintain over time.
Do you see any possibility of this being merged upstream? I do realize
that the upstream for android-tools is somewhat unusual, and that
getting contributions accepted might be more challenging than with
other open source projects. But still I'd like to hear about what has
been tried to push this upstream.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-01 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 20:56 [Buildroot] [PATCH 1/2] android-tools: Enable build for ext4 fsutils Keith Mok
2017-11-30 20:56 ` [Buildroot] [PATCH 2/2] android-tools: upport char, block, fifo, socket devices Keith Mok
2017-12-01 12:55 ` Thomas Petazzoni [this message]
2017-12-02 6:20 ` Keith Mok
2017-12-31 17:35 ` Thomas Petazzoni
2017-12-01 12:49 ` [Buildroot] [PATCH 1/2] android-tools: Enable build for ext4 fsutils Gary Bisson
2017-12-02 6:25 ` Keith Mok
2017-12-04 11:23 ` Gary Bisson
2017-12-05 17:21 ` Keith Mok
2017-12-31 17:35 ` Thomas Petazzoni
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=20171201135528.16e0c342@windsurf.lan \
--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