From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: stefanr@s5r6.in-berlin.de, netdev@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, stephan.gatzka@gmail.com
Subject: Re: [PATCH net-next (TAKE 4) 0/6] IPv6 over Firewire
Date: Tue, 26 Mar 2013 12:32:59 -0400 (EDT) [thread overview]
Message-ID: <20130326.123259.353351738581905875.davem@davemloft.net> (raw)
In-Reply-To: <51509696.6060600@linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Tue, 26 Mar 2013 03:25:26 +0900
> This is take 4 of supporting IPv6 over Firewire (IEEE 1394) based on
> RFC3146.
>
> Take 3->4:
> - Fix receiving 1394 ARP, which comes without arp$tha.
> - Remove rfc3146 unit directory on module exit.
> - other minor clean-ups - minimize diffs.
Series applied, thanks.
prev parent reply other threads:[~2013-03-26 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 18:25 [PATCH net-next (TAKE 4) 0/6] IPv6 over Firewire YOSHIFUJI Hideaki
2013-03-26 16:32 ` 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=20130326.123259.353351738581905875.davem@davemloft.net \
--to=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 \
--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).