From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>, Xuebing Wang <xbing6@gmail.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/7] timer: move APIs together according to their category
Date: Tue, 25 Feb 2014 17:38:32 +0100 [thread overview]
Message-ID: <530CC708.1080105@redhat.com> (raw)
In-Reply-To: <46E4D1A5-C128-4A03-B23F-BDB577F55B19@alex.org.uk>
Il 25/02/2014 17:25, Alex Bligh ha scritto:
>
> I'm generally in favour of this patch set or something like it. It's
> nicely constrained to 2 include files. It appears to touch no code.
> And it appears to makes things tidier.
>
> Stefan / Paolo? If you agree I will review in greater detail.
Sure, any help with reviews is welcome.
Paolo
next prev parent reply other threads:[~2014-02-25 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 13:36 [Qemu-devel] [PATCH 0/7] timer: move APIs together according to their category Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 1/7] timer: move QEMUTimerList functions together Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 2/7] timer: make QEMUTimerList functions private (remove from APIs) Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 3/7] timer: move QEMUClockType related functions together Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 4/7] timer: move QEMUTimerListGroup function to be below QEMUClockType Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 5/7] timer: move QEMUTimer related functions together Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 6/7] timer: move general utility " Xuebing Wang
2014-02-25 13:36 ` [Qemu-devel] [PATCH 7/7] timer: clean unnecessary #include and use minimal required #include Xuebing Wang
2014-02-25 16:25 ` [Qemu-devel] [PATCH 0/7] timer: move APIs together according to their category Alex Bligh
2014-02-25 16:38 ` Paolo Bonzini [this message]
2014-02-27 21:52 ` Alex Bligh
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=530CC708.1080105@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex@alex.org.uk \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xbing6@gmail.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.