From: "Michael S. Tsirkin" <mst@redhat.com>
To: yamahata@valinux.co.jp, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH RFC] pcie: clean up hot plug notification
Date: Mon, 25 Oct 2010 08:08:55 +0200 [thread overview]
Message-ID: <20101025060855.GA3559@redhat.com> (raw)
In-Reply-To: <20101025054941.GA3223@redhat.com>
On Mon, Oct 25, 2010 at 07:49:41AM +0200, Michael S. Tsirkin wrote:
> Simplify logic for hotplug notification, by tracking state of the
> logical interrupt condition. We then simply use this variable to make
> the interrupt decision, according to spec.
>
> API is made cleaner as we no longer force users to pass in
> old slot control value.
>
> Untested.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
I made some changes to this and other patches, and
pushed them out on my branch so everyone can take a look
there.
--
MST
next prev parent reply other threads:[~2010-10-25 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 5:49 [Qemu-devel] [PATCH RFC] pcie: clean up hot plug notification Michael S. Tsirkin
2010-10-25 6:08 ` Michael S. Tsirkin [this message]
2010-10-25 6:44 ` [Qemu-devel] " Isaku Yamahata
2010-10-25 6:46 ` Michael S. Tsirkin
2010-10-25 7:04 ` Isaku Yamahata
2010-10-25 8:05 ` Michael S. Tsirkin
2010-10-25 10:55 ` Michael S. Tsirkin
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=20101025060855.GA3559@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).