From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v2 0/4] package/dhcp
Date: Thu, 14 Jan 2016 21:27:43 -0200 [thread overview]
Message-ID: <56982eef6f13a_72e5f2a044692@ultri2.mail> (raw)
Hi Doug,
On Wed, 13 Jan 2016 16:38:27 -0600, Doug Kehn wrote:
[snip]
> Does the series need to retain the RFC tag, or is the handling of
> the embedded bind tar-ball acceptable?
Regarding the tag, I can't say for sure. I am still new to this mailing list.
Maybe someone else can advise?
I found an issue in the bind configuration when using an external toolchain.
BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_DHCP=y
BR2_PACKAGE_DHCP_CLIENT=y
I will post a suggestion in the appropriate patch from de series (1/4).
Regards,
Ricardo
next reply other threads:[~2016-01-14 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 23:27 Ricardo Martincoski [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 21:34 [Buildroot] [RFC PATCH v2 0/4] package/dhcp Ricardo Martincoski
2016-01-13 22:38 ` rdkehn at yahoo.com
2016-01-10 21:25 Doug Kehn
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=56982eef6f13a_72e5f2a044692@ultri2.mail \
--to=ricardo.martincoski@gmail.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