qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, agraf@suse.de,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-s390: add a reset function to virtio-s390 devices
Date: Wed, 16 Jan 2013 11:10:05 +0100	[thread overview]
Message-ID: <50F67C7D.3010103@redhat.com> (raw)
In-Reply-To: <50F63A2D.1010005@suse.de>

Il 16/01/2013 06:27, Andreas Färber ha scritto:
> Am 10.01.2013 15:40, schrieb Paolo Bonzini:
>> virtio-s390 devices are not being reset when their bus is.  To fix
>> this, add a reset method that forwards to virtio_reset.  This is
>> only needed because of the "strange" modeling of virtio devices;
>> the ->vdev link is being handled manually rather than through qdev.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  hw/s390-virtio-bus.c | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/hw/s390-virtio-bus.c b/hw/s390-virtio-bus.c
>> index 7e99175..1e3e4f0 100644
>> --- a/hw/s390-virtio-bus.c
>> +++ b/hw/s390-virtio-bus.c
>> @@ -505,6 +505,13 @@ static int s390_virtio_busdev_init(DeviceState *dev)
>>      return _info->init(_dev);
>>  }
>>  
>> +static void s390_virtio_busdev_reset(DeviceState *dev)
>> +{
>> +    VirtIOS390Device *_dev = (VirtIOS390Device *)dev;
> 
> Underscore alert. ;) What about naming the arg d and the variable dev?

True, but the file uses this convention throughout.

Paolo

  reply	other threads:[~2013-01-16 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 14:40 [Qemu-devel] [PATCH] virtio-s390: add a reset function to virtio-s390 devices Paolo Bonzini
2013-01-16  4:52 ` mdroth
2013-01-16  8:42   ` KONRAD Frédéric
2013-01-16 10:09     ` Paolo Bonzini
2013-01-16  5:27 ` Andreas Färber
2013-01-16 10:10   ` Paolo Bonzini [this message]
2013-01-16 10:31     ` Andreas Färber
2013-01-19 14:10 ` Paolo Bonzini
2013-01-19 14:20   ` Alexander Graf

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=50F67C7D.3010103@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).