From: "Andreas Färber" <afaerber@suse.de>
To: Artyom Tarasenko <atar4qemu@gmail.com>, blauwirbel@gmail.com
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH 4/4, master+QEMU 1.1] sun4u: implement interrupt clearing registers
Date: Sat, 12 May 2012 13:56:23 +0200 [thread overview]
Message-ID: <4FAE4FE7.1040905@suse.de> (raw)
In-Reply-To: <d874d7a29c7cb99cebf0bfc3a14615630f51e5e6.1336811825.git.atar4qemu@gmail.com>
Am 12.05.2012 11:15, schrieb Artyom Tarasenko:
> Implement registers for clearing OBIO and PCI interrupts
>
> Signed-off-by: Artyom Tarasenko <atar4qemu@gmail.com>
Implementing new registers is a feature, not a 1.1 bugfix...
Many of us would like to get patches committed and have to wait.
/-F
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-12 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 9:15 [Qemu-devel] [PATCH 0/4, master+QEMU 1.1] sparc64: let's boot Linux! Artyom Tarasenko
2012-05-12 9:15 ` [Qemu-devel] [PATCH 1/4] Implement address masking for SPARC v9 CPUs Artyom Tarasenko
2012-05-12 9:23 ` Artyom Tarasenko
2012-05-12 9:15 ` [Qemu-devel] [PATCH 2/4, master+QEMU 1.1] fix block loads broken in commit 30038fd818 Artyom Tarasenko
2012-05-12 9:15 ` [Qemu-devel] [PATCH 3/4, master+QEMU 1.1] sun4u: initialize OBIO interrupt mappings Artyom Tarasenko
2012-05-12 9:15 ` [Qemu-devel] [PATCH 4/4, master+QEMU 1.1] sun4u: implement interrupt clearing registers Artyom Tarasenko
2012-05-12 11:56 ` Andreas Färber [this message]
2012-05-12 12:32 ` Blue Swirl
2012-05-12 12:38 ` Andreas Färber
2012-05-12 13:08 ` Blue Swirl
2012-05-12 13:57 ` Andreas Färber
2012-05-12 14:34 ` Artyom Tarasenko
2012-05-12 13:00 ` Artyom Tarasenko
2012-05-12 10:01 ` [Qemu-devel] [PATCH 0/4, master+QEMU 1.1] sparc64: let's boot Linux! Blue Swirl
2012-05-12 10:49 ` Artyom Tarasenko
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=4FAE4FE7.1040905@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--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).