From: "Gao Feng" <gfree.wind@vip•163.com>
To: <davem@davemloft•net>, <jiri@resnulli•us>,
<mareklindner@neomailbox•ch>, <sw@simonwunderlich•de>,
<a@unstable•cc>, <kuznet@ms2•inr.ac.ru>, <jmorris@namei•org>,
<yoshfuji@linux-ipv6•org>, <kaber@trash•net>,
<steffen.klassert@secunet•com>, <herbert@gondor•apana.org.au>,
<netdev@vger•kernel.org>
Subject: RE: [PATCH net v4 00/12] Fix possbile memleaks when fail to register_netdevice
Date: Tue, 2 May 2017 19:10:29 +0800 [thread overview]
Message-ID: <000b01d2c334$b6ccda80$24668f80$@vip.163.com> (raw)
In-Reply-To: <cover.1493699451.git.gfree.wind@foxmail.com>
Hi all,
> From: gfree.wind@foxmail•com [mailto:gfree.wind@foxmail•com]
> Sent: Tuesday, May 2, 2017 1:59 PM
> drivers/net/dummy.c | 14 +++++++++++---
> drivers/net/ifb.c | 33 +++++++++++++++++++++++----------
> drivers/net/loopback.c | 15 ++++++++++++++-
> drivers/net/team/team.c | 15 ++++++++++++---
> drivers/net/veth.c | 15 ++++++++++++++-
> net/8021q/vlan_dev.c | 17 +++++++++++++----
> net/batman-adv/soft-interface.c | 18 +++++++++++++++---
> net/ipv4/ip_tunnel.c | 11 ++++++++++-
> net/ipv6/ip6_gre.c | 17 +++++++++++++----
> net/ipv6/ip6_tunnel.c | 11 ++++++++++-
> net/ipv6/ip6_vti.c | 11 ++++++++++-
> net/ipv6/sit.c | 17 +++++++++++++----
> 12 files changed, 158 insertions(+), 36 deletions(-)
>
> --
> v4: Make patches as one sery of patches, per David Miler
> v3: Split one patch to multiple commits, per David Ahern
> v2: Move the free in ndo_uninit when fail to register, per Herbert Xu
> v1: initial version
>
>
Because I sent these patches too fast today, so that my email server blocks
my account today.
The left patches (08~12) would be sent after my account is unlocked.
Maybe tomorrow.
I am very sorry about this, and try to change another mail server next time.
Best Regards
Feng
next prev parent reply other threads:[~2017-05-02 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 5:58 [PATCH net v4 00/12] Fix possbile memleaks when fail to register_netdevice gfree.wind
2017-05-02 5:58 ` [PATCH net v4 01/12] driver: dummy: Fix one possbile memleak " gfree.wind
2017-05-02 5:58 ` [PATCH net v4 02/12] driver: ifb: " gfree.wind
2017-05-02 5:58 ` [PATCH net v4 03/12] driver: loopback: " gfree.wind
2017-05-02 5:58 ` [PATCH net v4 04/12] driver: team: " gfree.wind
2017-05-02 5:58 ` [PATCH net v4 05/12] driver: veth: " gfree.wind
2017-05-02 5:58 ` [PATCH net v4 06/12] net: ip6_gre: " gfree.wind
2017-05-02 6:59 ` [PATCH net v4 07/12] ip6_tunnel: " gfree.wind
2017-05-02 11:10 ` Gao Feng [this message]
2017-05-02 13:34 ` [PATCH net v4 08/12] net: ip6_vti: " gfree.wind
2017-05-02 13:37 ` [PATCH net v4 09/12] net: ip_tunnel: " gfree.wind
2017-05-02 13:39 ` [PATCH net v4 10/12] net: sit: " gfree.wind
2017-05-02 13:41 ` [PATCH net v4 11/12] net: vlan: " gfree.wind
2017-05-02 14:17 ` [PATCH net v4 12/12] net: batman-adv: " gfree.wind
2017-05-02 19:30 ` [PATCH net v4 00/12] Fix possbile memleaks " David Miller
2017-05-03 0:33 ` Gao Feng
2017-05-07 22:25 ` David Miller
2017-05-08 4:18 ` Gao Feng
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='000b01d2c334$b6ccda80$24668f80$@vip.163.com' \
--to=gfree.wind@vip$(echo .)163.com \
--cc=a@unstable$(echo .)cc \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=jiri@resnulli$(echo .)us \
--cc=jmorris@namei$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=mareklindner@neomailbox$(echo .)ch \
--cc=netdev@vger$(echo .)kernel.org \
--cc=steffen.klassert@secunet$(echo .)com \
--cc=sw@simonwunderlich$(echo .)de \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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