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>,
Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
Subject: Re: net 2.6.25
Date: Wed, 14 Nov 2007 11:31:27 +0100 [thread overview]
Message-ID: <473ACE7F.5080007@fr.ibm.com> (raw)
In-Reply-To: <473AC169.1030202-3ImXcnM4P+0@public.gmane.org>
Denis V. Lunev wrote:
> Hello, guys!
>
> David has been opened net-2.6.25 tree yesterday, so we could send a new
> portion of NETNS there. If there are no objections, I'll send first six
> patches from OpenVZ GIT tomorrow, i.e. RTNL infrastructure, Packet &
> Unix sockets virtualization + some our /proc cleanups.
Did Pavel had time to look at RCU looking mechanism to replace
rtnl_lock/rtnl_unlock to protect the netns list ?
ps: isn't the openvz mailing list already subscribed to containers@
next prev parent reply other threads:[~2007-11-14 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 9:35 net 2.6.25 Denis V. Lunev
[not found] ` <473AC169.1030202-3ImXcnM4P+0@public.gmane.org>
2007-11-14 9:52 ` Eric W. Biederman
[not found] ` <m1ve8517dd.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-11-14 10:07 ` Denis V. Lunev
[not found] ` <473AC8C8.6070307-3ImXcnM4P+0@public.gmane.org>
2007-11-14 18:19 ` Eric W. Biederman
2007-11-14 10:31 ` Daniel Lezcano [this message]
[not found] ` <473ACE7F.5080007-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-14 10:54 ` Denis V. Lunev
[not found] ` <473AD3F0.1000604-3ImXcnM4P+0@public.gmane.org>
2007-11-14 16:03 ` Eric W. Biederman
2007-11-14 10:59 ` [Devel] " Pavel Emelyanov
[not found] ` <473AD4F5.40505-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-14 11:05 ` Daniel Lezcano
2007-11-15 17:15 ` Kir Kolyshkin
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=473ACE7F.5080007@fr.ibm.com \
--to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-3ImXcnM4P+0@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox