All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@sw.ru>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
	devel@openvz.org, Linux Containers <containers@lists.osdl.org>
Subject: [PATCH 0/6] preparations to enable netdevice notifiers inside a namespace (resend)
Date: Thu, 31 Jan 2008 14:59:49 +0300	[thread overview]
Message-ID: <47A1B835.7050600@sw.ru> (raw)

Here are some preparations and cleanups to enable network device/inet
address notifiers inside a namespace.

This set of patches has been originally sent last Friday. One cleanup
patch from the original series is dropped as wrong, thanks to Daniel
Lezcano.

             reply	other threads:[~2008-01-31 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 11:59 Denis V. Lunev [this message]
2008-01-31 12:00 ` [PATCH 1/6] [IPV4]: Fix memory leak on error path during FIB initialization Denis V. Lunev
2008-01-31 13:14   ` David Miller
2008-01-31 12:00 ` [PATCH 2/6] [IPV4]: Small style cleanup of the error path in rtm_to_ifaddr Denis V. Lunev
2008-01-31 12:00 ` [PATCH 3/6] [NETNS]: Process interface address manipulation routines in the namespace Denis V. Lunev
2008-01-31 12:00 ` [PATCH 4/6] [IPV4]: fib_sync_down rework Denis V. Lunev
2008-01-31 12:00 ` [PATCH 5/6] [NETNS]: Add a namespace mark to fib_info Denis V. Lunev
2008-01-31 12:00 ` [PATCH 6/6] [NETNS]: Lookup in FIB semantic hashes taking into account the namespace Denis V. Lunev
2008-01-31 14:58 ` [PATCH 0/6] preparations to enable netdevice notifiers inside a namespace (resend) Daniel Lezcano
     [not found]   ` <47A1E21C.40909-GANU6spQydw@public.gmane.org>
2008-01-31 16:47     ` Benjamin Thery
2008-01-31 17:46       ` Daniel Lezcano
2008-02-01  2:50 ` David Miller

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=47A1B835.7050600@sw.ru \
    --to=den@sw.ru \
    --cc=containers@lists.osdl.org \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=netdev@vger.kernel.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.