qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Mark McLoughlin <markmc@redhat.com>
Cc: linux-kernel@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] virtio-pci: do not oops on config change if driver not loaded
Date: Fri, 30 Jan 2009 12:15:40 +1030	[thread overview]
Message-ID: <200901301215.40312.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1233243136-8028-1-git-send-email-markmc@redhat.com>

On Friday 30 January 2009 02:02:16 Mark McLoughlin wrote:
> The host really shouldn't be notifying us of config changes
> before the device status is VIRTIO_CONFIG_S_DRIVER or
> VIRTIO_CONFIG_S_DRIVER_OK.
> 
> However, if we do happen to be interrupted while we're not
> attached to a driver, we really shouldn't oops.

Thanks, applied!

Rusty.

      reply	other threads:[~2009-01-30  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 15:32 [Qemu-devel] [PATCH] virtio-pci: do not oops on config change if driver not loaded Mark McLoughlin
2009-01-30  1:45 ` Rusty Russell [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=200901301215.40312.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.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).