netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/6] ipv6: ip6mr: support multiple independant multicast routing instances
Date: Wed, 12 May 2010 23:31:30 -0700 (PDT)	[thread overview]
Message-ID: <20100512.233130.104075508.davem@davemloft.net> (raw)
In-Reply-To: <1273586551-3521-1-git-send-email-kaber@trash.net>

From: kaber@trash.net
Date: Tue, 11 May 2010 16:02:25 +0200

> The following patches add support for multiple independant IPv6 multicast
> routing instances. This can be useful to seperate traffic when building
> a multicast router that is serving multiple independant networks.
> 
> The patchset is pretty much a straight forward port from IPv4 with no
> significant differences.
 ...
> These patches have been tested using pim6sd and mrd6.
> 
> Please apply or pull from:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/kaber/ipmr-2.6.git master

Pulled, thanks!

      parent reply	other threads:[~2010-05-13  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 14:02 [PATCH 0/6] ipv6: ip6mr: support multiple independant multicast routing instances kaber
2010-05-11 14:02 ` [PATCH 1/6] ipv6: ip6mr: move unres_queue and timer to per-namespace data kaber
2010-05-11 14:02 ` [PATCH 2/6] ipv6: ip6mr: remove net pointer from struct mfc6_cache kaber
2010-05-11 14:02 ` [PATCH 3/6] ipv6: ip6mr: convert struct mfc_cache to struct list_head kaber
2010-05-11 14:02 ` [PATCH 4/6] ipv6: ip6mr: move mroute data into seperate structure kaber
2010-05-11 14:02 ` [PATCH 5/6] ipv6: ip6mr: support multiple tables kaber
2010-05-11 14:02 ` [PATCH 6/6] ipv6: ip6mr: add support for dumping routing tables over netlink kaber
2010-05-13  6:31 ` David Miller [this message]

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=20100512.233130.104075508.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kaber@trash.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).