From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH 0/3] HPET patches
Date: Wed, 6 Nov 2013 17:45:04 +0000 [thread overview]
Message-ID: <1383759907-624-1-git-send-email-andrew.cooper3@citrix.com> (raw)
This reduced series consists of the non-contentious and tangential patchs from
my large HPET series, which have undergone one round of review already. They
are now in a state where I believe they can go straight in.
I am currently in the process of trying to adjust the remainder of the series
and strip small indepent changes out of the mamoth patch, in an effort to
reduce its complexity.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
next reply other threads:[~2013-11-06 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 17:45 Andrew Cooper [this message]
2013-11-06 17:45 ` [PATCH 1/3] x86/acpi: Warn about multiple HPET tables Andrew Cooper
2013-11-06 17:45 ` [PATCH 2/3] x86/hpet: Fix ambiguity in broadcast info message Andrew Cooper
2013-11-06 17:45 ` [PATCH 3/3] x86/msi: Refactor msi_compose_message() to not require an irq_desc Andrew Cooper
2013-11-06 22:58 ` [PATCH 0/3] HPET patches Tim Deegan
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=1383759907-624-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).