From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: Supporting patches for netns/netdev (v2)
Date: Tue, 09 Feb 2010 17:05:31 -0500 [thread overview]
Message-ID: <4B71DC2B.1070107@cs.columbia.edu> (raw)
In-Reply-To: <1265749870-13989-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Both look good.
Oren.
Dan Smith wrote:
> These two patches make a couple of small (yet potentially controversial)
> changes to the cleanup of the objhash and the restore_obj() function.
> The way network devices have to get torn down (in the case of a failed
> restore) and the way I need to create veth pairs are why I need this
> sort of functionality.
>
> Each could be done a number of different ways, but I'm hoping these
> quick changes are acceptable.
>
> Version 2, with changes to patch #1 only.
>
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>
next prev parent reply other threads:[~2010-02-09 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 21:11 Supporting patches for netns/netdev (v2) Dan Smith
[not found] ` <1265749870-13989-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-09 21:11 ` [PATCH 1/2] Make restore_obj() tolerate a preexisting object in the hash (v2) Dan Smith
2010-02-09 21:11 ` [PATCH 2/2] Move ckpt_objhash_free() to before we destroy the deferqueues Dan Smith
2010-02-09 22:05 ` Oren Laadan [this message]
[not found] ` <4B71DC2B.1070107-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-09 22:10 ` Supporting patches for netns/netdev (v2) Dan Smith
[not found] ` <87y6j2giwl.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-02-09 22:11 ` Oren Laadan
2010-02-09 22:32 ` Serge E. Hallyn
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=4B71DC2B.1070107@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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.