From: "Gao Feng" <gfree.wind@foxmail.com>
To: "'David Miller'" <davem@davemloft.net>
Cc: <sd@queasysnail.net>, <phil@nwl.cc>, <stephen@networkplumber.org>,
<zhangshengju@cmss.chinamobile.com>, <netdev@vger.kernel.org>
Subject: RE: [PATCH net v3] driver: dummy: Fix one possbile memleak when fail to register_netdevice
Date: Tue, 2 May 2017 10:15:00 +0800 [thread overview]
Message-ID: <003f01d2c2e9$e74987d0$b5dc9770$@foxmail.com> (raw)
In-Reply-To: <20170430.225336.754367857537363635.davem@davemloft.net>
> From: David Miller [mailto:davem@davemloft.net]
> Sent: Monday, May 1, 2017 10:54 AM
>
> Please, Gao, submit this as a proper, numbered, patch series with a proper
> header posting.
>
> That way you can explain why you took this strategy to fix this problem,
> compared to your original approach.
>
> Thanks.
OK, no problem.
Regards
Feng
prev parent reply other threads:[~2017-05-02 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 3:39 [PATCH net v3] driver: dummy: Fix one possbile memleak when fail to register_netdevice gfree.wind
2017-05-01 2:53 ` David Miller
2017-05-02 2:15 ` Gao Feng [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='003f01d2c2e9$e74987d0$b5dc9770$@foxmail.com' \
--to=gfree.wind@foxmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=sd@queasysnail.net \
--cc=stephen@networkplumber.org \
--cc=zhangshengju@cmss.chinamobile.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).