From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: David Miller <davem@davemloft.net>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net, netdev@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: [git pull] firewire net: resource management improvements
Date: Fri, 22 Mar 2013 12:34:23 +0900 [thread overview]
Message-ID: <1363923263.16608.14.camel@cirrhata> (raw)
In-Reply-To: <20130313163742.73a3a842@stein>
Dave,
would you consider pulling this one to net-next, please?
I can prepare rebased tree, if you want.
Thanks.
--yoshfuji
Stefan Richter wrote:
> David,
>
> please pull from the tag "firewire-net-resource-mgt" at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git firewire-net-resource-mgt
>
> to receive the following firewire-net driver changes:
> - fix memory leak and kmap leak at shutdown
> - release IR DMA context already at ifdown rather than shutdown
> (many controllers have got only 4 of them, so let's not hold it
> longer than strictly necessary)
> - misc startup/shutdown changes which prepare for later addition
> of IPv6-over-1394 support
>
> 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(-)
>
> Thanks,
next prev parent reply other threads:[~2013-03-22 3:31 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
2013-03-13 14:24 ` David Miller
2013-03-13 15:37 ` [git pull] " Stefan Richter
2013-03-22 3:34 ` YOSHIFUJI Hideaki [this message]
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=1363923263.16608.14.camel@cirrhata \
--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 \
/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).