From: Ying Xue <ying.xue@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: <jon.maloy@ericsson.com>, <erik.hugne@ericsson.com>,
<netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>
Subject: Re: [PATCH net-next] tipc: fix a slab object leak
Date: Wed, 1 Apr 2015 11:16:12 +0800 [thread overview]
Message-ID: <551B62FC.8030303@windriver.com> (raw)
In-Reply-To: <20150331.231309.610369858855748160.davem@davemloft.net>
On 04/01/2015 11:13 AM, David Miller wrote:
> This bug exists in 'net', so that's where I'm applying it.
>
> Can you please target your patches properly, I shouldn't be
> doing this kind of work for you.
Sure, I will recreate the patch targeted at "net" tree.
Thanks,
Ying
next prev parent reply other threads:[~2015-04-01 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 1:42 [PATCH net-next] tipc: fix a slab object leak Ying Xue
2015-04-01 3:13 ` David Miller
2015-04-01 3:16 ` Ying Xue [this message]
2015-04-01 4:19 ` 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=551B62FC.8030303@windriver.com \
--to=ying.xue@windriver.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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).