netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, fubar@us.ibm.com, andy@greyhouse.net,
	kaber@trash.net, stephen@networkplumber.org,
	kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	edumazet@google.com
Subject: [patch net-next v2 0/3] add support for peer notifications and igmp rejoins for team
Date: Sat, 20 Jul 2013 12:13:51 +0200	[thread overview]
Message-ID: <1374315234-7096-1-git-send-email-jiri@resnulli.us> (raw)

The middle patch adjusts core infrastructure so the bonding code can be
generalized and reused by team.

v1->v2: using msecs_to_jiffies() as suggested by Eric

Jiri Pirko (3):
  team: add peer notification
  net: convert resend IGMP to notifier event
  team: add support for sending multicast rejoins

 drivers/net/bonding/bond_main.c |  44 ++--------
 drivers/net/team/team.c         | 176 ++++++++++++++++++++++++++++++++++++++++
 include/linux/if_team.h         |  14 +++-
 include/linux/igmp.h            |   1 -
 include/linux/netdevice.h       |   1 +
 net/8021q/vlan.c                |   1 +
 net/bridge/br_notify.c          |   5 ++
 net/ipv4/igmp.c                 |  46 +++++++++--
 8 files changed, 245 insertions(+), 43 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2013-07-20 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 10:13 Jiri Pirko [this message]
2013-07-20 10:13 ` [patch net-next v2 1/3] team: add peer notification Jiri Pirko
2013-07-20 10:13 ` [patch net-next v2 2/3] net: convert resend IGMP to notifier event Jiri Pirko
2013-07-22 16:26   ` [net-next,v2,2/3] " Veaceslav Falico
2013-07-20 10:13 ` [patch net-next v2 3/3] team: add support for sending multicast rejoins Jiri Pirko
2013-07-23 23:54 ` [patch net-next v2 0/3] add support for peer notifications and igmp rejoins for team 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=1374315234-7096-1-git-send-email-jiri@resnulli.us \
    --to=jiri@resnulli.us \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fubar@us.ibm.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=yoshfuji@linux-ipv6.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).