From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 0/5] Initial IPv6 support
Date: Fri, 18 Jan 2013 09:20:41 +0100 [thread overview]
Message-ID: <20130118092041.0c827374@lilith> (raw)
In-Reply-To: <1358472932-32083-1-git-send-email-judge.packham@gmail.com>
Hi Chris,
On Fri, 18 Jan 2013 14:35:27 +1300, Chris Packham
<judge.packham@gmail.com> wrote:
> From: Chris Packham <chris.packham@alliedtelesis.co.nz>
>
> This series so far covers the introduction of a IP6addr_t and
> printing/parsing of addresses.
As a general comment, I heartily welcome IPv6 support (even though I
suspect there is quite a lot to be done on it, if only configuration),
but I wonder how this fits in with the general line of not adding dead
code in U-Boot. Will we make an exception for IPv6 and accept this RFC
once it is officially submitted? Or do we collect small, reviewable
RFCs for various IPv6 aspects but apply them in one go? Or do we create
a branch or tree where IPv6 will get integrated step by step until
solid enough for mainline inclusion? Or was this decided already and I
missed it?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-01-18 8:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 1:35 [U-Boot] [RFC PATCH v2 0/5] Initial IPv6 support Chris Packham
2013-01-18 1:35 ` [U-Boot] [RFC PATCH v2 1/5] Initial net6.h Chris Packham
2013-01-18 21:15 ` Kim Phillips
2013-01-18 1:35 ` [U-Boot] [RFC PATCH v2 2/5] lib/vsprintf.c: add IPv6 compressed format %pI6c Chris Packham
2013-01-18 1:35 ` [U-Boot] [RFC PATCH v2 3/5] lib/net_utils.c: make string_to_ip stricter Chris Packham
2013-01-18 1:35 ` [U-Boot] [RFC PATCH v2 4/5] lib/net_utils.c: add string_to_ip6 Chris Packham
2013-01-18 1:35 ` [U-Boot] [RFC PATCH v2 5/5] common.h: add getenv_IP6addr Chris Packham
2013-01-18 8:20 ` Albert ARIBAUD [this message]
2013-01-18 9:39 ` [U-Boot] [RFC PATCH v2 0/5] Initial IPv6 support Chris Packham
2013-01-18 10:16 ` Sergey Lapin
2013-01-18 10:44 ` Wolfgang Denk
2013-01-18 18:41 ` Joe Hershberger
2013-01-20 9:47 ` Chris Packham
2013-01-20 9:44 ` Chris Packham
2013-01-20 21:00 ` Albert ARIBAUD
2013-01-20 21:25 ` Chris Packham
2013-01-21 0:51 ` Chris Packham
2013-01-21 12:37 ` Wolfgang Denk
2013-01-18 10:25 ` Wolfgang Denk
2013-01-18 10:23 ` Wolfgang Denk
2013-01-20 9:24 ` Chris Packham
2013-01-21 12:39 ` Wolfgang Denk
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=20130118092041.0c827374@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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