From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jing Wang <windsdaemon@gmail.com>,
davem@davemloft.net, jhs@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] net:sched fix a bug about memery leak
Date: Thu, 24 Oct 2013 18:10:00 +0400 [thread overview]
Message-ID: <52692A38.8040705@cogentembedded.com> (raw)
In-Reply-To: <1382605964-2693-1-git-send-email-windsdaemon@gmail.com>
Hello.
On 10/24/2013 01:12 PM, Jing Wang wrote:
s/mememry/memory/ in the subject.
> From: Jing Wang <windsdaemon@gmail.com>
> the code isn't properly release memory
s/release/releasing/.
> Signed-off-by: Jing Wang <windsdaemon@gmail.com>
WBR, Sergei
next prev parent reply other threads:[~2013-10-24 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 9:12 [PATCH 1/1] net:sched fix a bug about memery leak Jing Wang
2013-10-24 9:33 ` Eric Dumazet
2013-10-24 14:07 ` Christoph Paasch
2013-10-24 14:23 ` Christoph Paasch
2013-10-24 14:10 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-24 9:06 Jing Wang
2013-10-24 14:05 ` Sergei Shtylyov
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=52692A38.8040705@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=windsdaemon@gmail.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).