From: majianpeng <majianpeng@gmail.com>
To: bfields <bfields@fieldses.org>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] Fix two memleak
Date: Tue, 29 Jan 2013 13:16:00 +0800 [thread overview]
Message-ID: <201301291315490872700@gmail.com> (raw)
SmlhbnBlbmcgTWEgKDIpOg0KICBuZnNkOiBGaXggbWVtbGVhay4NCiAgbmZzZDogRml4IG1lbWxl
YWsuDQoNCiBmcy9uZnNkL2V4cG9ydC5jICAgIHwgICAgMSArDQogZnMvbmZzZC9uZnM0c3RhdGUu
YyB8ICAgIDIgKysNCiAyIGZpbGVzIGNoYW5nZWQsIDMgaW5zZXJ0aW9ucygrKQ0KDQotLSANCjEu
Ny45LjUNCg==
reply other threads:[~2013-01-29 5:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201301291315490872700@gmail.com \
--to=majianpeng@gmail.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.