From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] cubieboard: [PATCH] ipconfig: add nameserver IPs to kernel-parameter ip=
Date: Tue, 21 Jul 2015 23:26:12 +0200 [thread overview]
Message-ID: <20150721232612.6af50062@free-electrons.com> (raw)
In-Reply-To: <1437443362-8025-4-git-send-email-fancp2007@gmail.com>
Dear Scott Fan,
On Tue, 21 Jul 2015 09:49:22 +0800, Scott Fan wrote:
> Signed-off-by: Scott Fan <fancp2007@gmail.com>
> ---
> .../5e953778a2aab04929a5e7b69f53dc26e39b079e.patch | 133 +++++++++++++++++++++
> configs/cubieboard2_defconfig | 1 +
> configs/cubieboard_defconfig | 1 +
> configs/cubietruck_defconfig | 1 +
> 4 files changed, 136 insertions(+)
> create mode 100644 board/cubietech/cubieboard/5e953778a2aab04929a5e7b69f53dc26e39b079e.patch
Thanks for the patch, but unfortunately, it's not acceptable. It's
clearly a feature patch for the kernel, and we generally don't accept
feature patches in Buildroot. If you want to be able to set the
nameserver from the ip= parameter, then please submit a patch to the
Linux kernel network maintainers and get it accepted. We don't want to
carry such patches forever in the Buildroot tree.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-21 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 1:49 [Buildroot] [PATCH 3/4] cubieboard: update build support for cubieboard 1/2/3 Scott Fan
2015-07-21 1:49 ` [Buildroot] [PATCH 4/4] cubieboard: [PATCH] ipconfig: add nameserver IPs to kernel-parameter ip= Scott Fan
2015-07-21 21:26 ` Thomas Petazzoni [this message]
2015-07-21 21:38 ` [Buildroot] [PATCH 3/4] cubieboard: update build support for cubieboard 1/2/3 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=20150721232612.6af50062@free-electrons.com \
--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