From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Stephan Gatzka <stephan.gatzka@gmail.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: netdev@vger.kernel.org, linux1394-devel@lists.sourceforge.net,
yoshfuji@linux-ipv6.org
Subject: [RFC PATCH 0/6] IPv6 over Firewire (PoC)
Date: Sat, 12 Jan 2013 23:20:53 +0900 [thread overview]
Message-ID: <50F17145.9050104@linux-ipv6.org> (raw)
This is my proof of concept changes over the tree.
Code compiles, but untested.
Full changesets are also availble at:
http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=gitroot/yoshfuji/linux-2.6-dev.git;a=shortlog;h=refs/heads/v3.7%2Bnet-next%2Bfirewire
I think firewire/net bits should be moved to firewire/net_core.c or something,
which is compiled statically even if FIREWIRE_NET = m.
YOSHIFUJI Hideaki (6):
ndisc: Move ndisc_opt_addr_space() to include/net/ndisc.h.
ndisc: Pass net_device to ndisc_fill_addr_option().
firewire net: Export fwnet_peerinfo structure for ieee1394-specific
peer information in ARP/NDP.
firewire net: Export peerinfo handlers.
firewire net: IPv6 support (RFC3146).
ipv6: IPv6 over IEEE1394 (RFC3146) support.
drivers/firewire/Kconfig | 8 +++
drivers/firewire/net.c | 125 ++++++++++++++++++++++++++++------------------
include/net/firewire.h | 21 ++++++++
include/net/ndisc.h | 20 +++++++-
net/ipv6/addrconf.c | 4 +-
net/ipv6/ndisc.c | 71 +++++++++++++++++++++-----
net/ipv6/route.c | 2 +
7 files changed, 188 insertions(+), 63 deletions(-)
create mode 100644 include/net/firewire.h
--
1.7.9.5
reply other threads:[~2013-01-12 14:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50F17145.9050104@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--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).