netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: netdev@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Cc: stephan.gatzka@gmail.com, davem@davemloft.net,
	stefanr@s5r6.in-berlin.de, yoshfuji@linux-ipv6.org
Subject: [net-next (TAKE 2) 0/4] IPv6 over Firewire
Date: Sun, 10 Feb 2013 18:02:02 +0900	[thread overview]
Message-ID: <5117620A.4050005@linux-ipv6.org> (raw)

This is TAKE 2 of IPv6 over IEEE1394(Firewire) (RFC3146) support
by extended MAC approach.

YOSHIFUJI Hideaki (4):
  firewire net: Accept IPv4 and ARP only.
  firewire net: Send L2 multicast via GASP.
  firewire net, ipv4 arp: Extend hardware address and remove
    driver-level packet inspection.
  ipv6: IPv6 over Firewire (RFC3146) support.

 drivers/firewire/Kconfig |    6 +-
 drivers/firewire/net.c   |  329 +++++++++++++++++++++-------------------------
 include/linux/if_arp.h   |   12 +-
 include/net/firewire.h   |   25 ++++
 net/ipv4/arp.c           |   18 ++-
 net/ipv6/addrconf.c      |   20 ++-
 6 files changed, 222 insertions(+), 188 deletions(-)
 create mode 100644 include/net/firewire.h

-- 
1.7.9.5

             reply	other threads:[~2013-02-10  9:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  9:02 YOSHIFUJI Hideaki [this message]
2013-02-10 10:29 ` [net-next (TAKE 2) 0/4] IPv6 over Firewire Stephan Gatzka
2013-02-10 10:48   ` YOSHIFUJI Hideaki
2013-02-10 12:48     ` Stephan Gatzka
2013-02-10 15:05       ` YOSHIFUJI Hideaki
2013-02-11 10:32         ` Stephan Gatzka
2013-02-11 13:13           ` YOSHIFUJI Hideaki
2013-02-12 19:46             ` Stephan Gatzka
2013-03-01 10:28               ` Stephan Gatzka
2013-03-01 19:44               ` Stephan Gatzka
2013-03-10 10:03                 ` Stephan Gatzka
2013-02-13 12:45             ` Stephan Gatzka
2013-02-13 17:08               ` YOSHIFUJI Hideaki

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=5117620A.4050005@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stephan.gatzka@gmail.com \
    /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).