netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
	David Miller <davem@davemloft.net>
Cc: linux1394-devel@lists.sourceforge.net, netdev <netdev@vger.kernel.org>
Subject: Re: [RFC net-next 00/11] firewire net: resource management improvements
Date: Wed, 13 Mar 2013 15:19:19 +0100	[thread overview]
Message-ID: <20130313151919.68068bae@stein> (raw)
In-Reply-To: <5139419A.2040309@linux-ipv6.org>

On Mar 08 YOSHIFUJI Hideaki wrote:
> This series of patches tries to improve resource management of IP over Firewire
> device.
> 
> Because upcoming IPv6 over Firewire patch depends on this series, it would
> be better to let this series of patches go through Dave's net-next tree, if
> firewire people do not mind.
> 
> --yoshfuji
> 
> YOSHIFUJI Hideaki (11):
>   firewire net: No need to reset dev->local_fifo after failure of
>     fw_core_add_address_handler().
>   firewire net: Introduce fwnet_fifo_{start,stop}() helpers.
>   firewire net: Setup broadcast and local fifo independently.
>   firewire net: Check dev->broadcast_state inside
>     fwnet_broadcast_start().
>   firewire net: Fix memory leakage in fwnet_remove().
>   firewire net: Clear dev->broadcast_rcv_context and
>     dev->broadcast_state after destruction of context.
>   firewire net: Omit checking dev->broadcast_rcv_context in
>     fwnet_broadcast_start().
>   firewire net: Fix leakage of kmap for broadcast receive buffer.
>   firewire net: Allocate dev->broadcast_rcv_buffer_ptrs early.
>   firewire net: Introduce fwnet_broadcast_stop() to destroy broadcast
>     resources.
>   firewire net: Release broadcast/fifo resources on ifdown.
> 
>  drivers/firewire/net.c |  177 ++++++++++++++++++++++++++++--------------------
>  1 file changed, 105 insertions(+), 72 deletions(-)
> 

All 11 patches:
Reviewed-by: Stefan Richter <stefanr@s5r6.in-berlin.de>

ACK for routing this through net-next.  David, do you need me to respond to
each individual patch with the reviewer tag?  Or since I already have the
patches in a quilt series locally, I could commit them to a branch at
linux1394.git and send you a pull request.
-- 
Stefan Richter
-=====-===-= --== -==-=
http://arcgraph.de/sr/

  reply	other threads:[~2013-03-13 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  1:40 [RFC net-next 00/11] firewire net: resource management improvements YOSHIFUJI Hideaki
2013-03-13 14:19 ` Stefan Richter [this message]
2013-03-13 14:24   ` David Miller
2013-03-13 15:37     ` [git pull] " Stefan Richter
2013-03-22  3:34       ` YOSHIFUJI Hideaki
2013-03-22 14:35         ` David Miller
2013-03-22 21:21           ` Stefan Richter
2013-03-24 21:32             ` 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=20130313151919.68068bae@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=davem@davemloft.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.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).