From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: "Denis V. Lunev" <den-3ImXcnM4P+0@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
Pavel Emelianov <xemul-3ImXcnM4P+0@public.gmane.org>
Subject: Re: net-2.6.25-netns branch on git.openvz.org
Date: Thu, 15 Nov 2007 14:00:49 +0100 [thread overview]
Message-ID: <473C4301.6060507@fr.ibm.com> (raw)
In-Reply-To: <473C35F1.9030901-3ImXcnM4P+0@public.gmane.org>
Denis V. Lunev wrote:
> Hi, All!
>
> I have ported what is ready to send to netdev to 2.6.25 and created
> appropriate branches on git.openvz.org, namely
> - net-2.6.25 aka Miller's 2.6.25 tree
> - net-2.6.25-netns with ready patches
resyncing ... thanks :)
I will send in a few moments a first round for ipv6 taking into account
ip6_fib.
There some other pending patches I will send, I hope before the end of
the week.
I am a little lost with what we want to send for net-2.6.25. I mean we
planned to send af_unix, af_packet, af_netlink, af_inet and af_inet6.
What is the level of functionnality we want to provide with ipv4 and
ipv6. For example we have addresss autoconfiguration for ipv6, shall we
send it ?
What about the todo list Pavel planned to do ?
next prev parent reply other threads:[~2007-11-15 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 12:05 net-2.6.25-netns branch on git.openvz.org Denis V. Lunev
[not found] ` <473C35F1.9030901-3ImXcnM4P+0@public.gmane.org>
2007-11-15 13:00 ` Daniel Lezcano [this message]
[not found] ` <473C4301.6060507-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-15 13:14 ` Pavel Emelyanov
[not found] ` <473C4627.7080505-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-15 13:20 ` Daniel Lezcano
2007-11-15 13:26 ` Denis V. Lunev
[not found] ` <473C48F0.3010909-3ImXcnM4P+0@public.gmane.org>
2007-11-15 13:31 ` Daniel Lezcano
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=473C4301.6060507@fr.ibm.com \
--to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-3ImXcnM4P+0@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=xemul-3ImXcnM4P+0@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.