From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Loïc Minier" <lool@dooz.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] Detect and use GCC atomic builtins for locking
Date: Sun, 28 Feb 2010 00:26:19 +0000 [thread overview]
Message-ID: <201002280026.19368.paul@codesourcery.com> (raw)
In-Reply-To: <1266613360-23069-1-git-send-email-lool@dooz.org>
>diff --git a/qemu-lock.h b/qemu-lock.h
This code isn't used in any interesting ways, it should be removed..
Paul
prev parent reply other threads:[~2010-02-28 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 21:02 [Qemu-devel] [PATCH 1/2] Detect and use GCC atomic builtins for locking Loïc Minier
2010-02-19 21:02 ` [Qemu-devel] [PATCH 2/2] Make spinlock_t types volatile Loïc Minier
2010-02-19 21:42 ` [Qemu-devel] [PATCH 1/2] Detect and use GCC atomic builtins for locking malc
2010-02-20 8:16 ` Loïc Minier
2010-02-20 8:28 ` malc
2010-02-20 9:10 ` Loïc Minier
2010-02-20 17:57 ` malc
2010-02-22 10:25 ` Loïc Minier
2010-02-22 10:47 ` malc
2010-02-28 0:26 ` Paul Brook [this message]
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=201002280026.19368.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=lool@dooz.org \
--cc=qemu-devel@nongnu.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 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).