From: Jeff Dike <jdike@addtoit.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org,
User-mode-linux-devel@lists.sourceforge.net,
Steven James <pyro@linuxlabs.com>,
Roland McGrath <roland@redhat.com>,
Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [discuss] [RFC] [PATCH] Double syscall exit traces on x86_64
Date: Fri, 26 May 2006 10:13:45 -0400 [thread overview]
Message-ID: <20060526141345.GA4152@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200605261236.26814.ak@suse.de>
On Fri, May 26, 2006 at 12:36:26PM +0200, Andi Kleen wrote:
> I believe this patch is the correct fix. Can you confirm it works for you?
Looks good, thanks.
Jeff
next prev parent reply other threads:[~2006-05-26 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:24 [RFC] [PATCH] Double syscall exit traces on x86_64 Jeff Dike
2006-05-26 10:36 ` [discuss] " Andi Kleen
2006-05-26 14:13 ` Jeff Dike [this message]
2006-06-01 19:07 ` [uml-devel] " Blaisorblade
2006-06-02 15:13 ` [uml-devel] " Jeff Dike
2006-06-02 15:38 ` Steven James
2006-06-02 17:16 ` Blaisorblade
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=20060526141345.GA4152@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=blaisorblade@yahoo.it \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pyro@linuxlabs.com \
--cc=roland@redhat.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