From: Ian Campbell <ian.campbell@citrix.com>
To: "Liuqiming (John)" <john.liuqiming@huawei.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Yanqiangjun <yanqiangjun@huawei.com>,
David Scott <dave.scott@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: oxenstored memory leak? seems related with XSA-38
Date: Mon, 22 Jul 2013 22:37:07 +0100 [thread overview]
Message-ID: <1374529027.6623.75.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <0E6BCB61859D7F4EB9CAC75FC6EE6FF8437B747C@szxeml526-mbs.china.huawei.com>
On Mon, 2013-07-22 at 12:08 +0000, Liuqiming (John) wrote:
> Here is my patch, please let me know if I did anything wrong. (this is my first patch for xen :)
Applied, thanks.
Generally a fresh email with the patch and the changelog inline in the
body is preferred, http://wiki.xen.org/wiki/Submitting_Xen_Patches has
some hints and descriptions of handy tools...
Ian.
next prev parent reply other threads:[~2013-07-22 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C462DF05CCBDDC42BC667291C037376D39205981@SZXEML506-MBS.china.huawei.com>
2013-07-05 3:14 ` oxenstored memory leak? seems related with XSA-38 Liuqiming (John)
2013-07-05 9:07 ` Liuqiming (John)
2013-07-15 12:13 ` David Scott
2013-07-16 5:19 ` Liuqiming (John)
2013-07-16 9:46 ` Ian Campbell
2013-07-16 9:56 ` David Scott
2013-07-19 11:56 ` Ian Campbell
2013-07-22 12:08 ` Liuqiming (John)
2013-07-22 21:37 ` Ian Campbell [this message]
2013-07-04 2:48 Liuqiming (John)
2013-07-04 8:52 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2013-07-01 13:47 Liuqiming (John)
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=1374529027.6623.75.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.scott@eu.citrix.com \
--cc=john.liuqiming@huawei.com \
--cc=xen-devel@lists.xen.org \
--cc=yanqiangjun@huawei.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 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.