From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] trace security fixes
Date: Mon, 28 Jun 2010 13:02:31 +0100 [thread overview]
Message-ID: <4C28AB77020000780000864F@vpn.id2.novell.com> (raw)
In-Reply-To: <C84E4247.18BC9%keir.fraser@eu.citrix.com>
>>> On 28.06.10 at 13:12, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> Both of these xentrace patches need an Ack from George Dunlap. Also I will
> need to know if they belong in any tree other than xen-unstable.
I would see them both as candidates for 4.0.x at least.
Jan
next prev parent reply other threads:[~2010-06-28 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 10:39 [PATCH] trace security fixes Jan Beulich
2010-06-28 11:12 ` Keir Fraser
2010-06-28 12:02 ` Jan Beulich [this message]
2010-06-29 14:21 ` George Dunlap
2010-06-29 15:29 ` [PATCH 0/6] trace: miscellaneous fixes Jan Beulich
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=4C28AB77020000780000864F@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).