All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Li <junmuzi@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, aliguori@amazon.com,
	"Michael S. Tsirkin" <mst@redhat.com>,
	juli@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
	anthony@codemonkey.ws, pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2] Add remove_boot_device_path() function for hot-unplug device
Date: Mon, 19 May 2014 21:44:14 +0800	[thread overview]
Message-ID: <537A0AAE.2030902@gmail.com> (raw)
In-Reply-To: <87iop2i6cj.fsf@blackfin.pond.sub.org>


On 05/19/2014 03:18 PM, Markus Armbruster wrote:
> Jun Li <junmuzi@gmail.com> writes:
>
>> On 05/15/2014 11:07 PM, Michael S. Tsirkin wrote:
>>> On Wed, Apr 16, 2014 at 10:20:57PM +0800, Jun Li wrote:
> [...]
>>>> diff --git a/vl.c b/vl.c
>>>> index 9975e5a..1713c68 100644
>>>> --- a/vl.c
>>>> +++ b/vl.c
>>>> @@ -1184,6 +1184,22 @@ void add_boot_device_path(int32_t bootindex, DeviceState *dev,
>>>>        QTAILQ_INSERT_TAIL(&fw_boot_order, node, link);
>>>>    }
>>>>    +void remove_boot_device_path(int32_t bootindex, DeviceState
>>>> *dev,
>>>> +                             const char *suffix)
>>> Why do we need suffix here?
>>> It seems unused.
> dev is unused as well.
>
>> Hi Michael,
>>
>> I just want to keep the same as function "add_boot_device_path". Such as:
>> void add_boot_device_path(int32_t bootindex, DeviceState *dev,
>>                            const char *suffix)
> Functions creating something commonly take different arguments than the
> function to destroy it.
ok, I will submit a update version for this patch.
>
>> I also find another function has define mon, but not be used in this function. Such as:
>> ---file vl.c---
>> do_usb_del(Monitor *mon, const QDict *qdict)
>> {
>>      const char *devname = qdict_get_str(qdict, "devname");
>>      if (usb_device_del(devname) < 0) {
>>          error_report("could not delete USB device '%s'", devname);
>>      }
>> }
> This one has a compelling reason: it's a mon_cmd_t mhandler.cmd
> callback.
oh, thanks for your explanation.

Best Regards,
Jun Li

      reply	other threads:[~2014-05-19 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1397658057-12086-1-git-send-email-junmuzi@gmail.com>
     [not found] ` <1398158504.30055.12.camel@localhost.localdomain>
2014-05-11  3:07   ` [Qemu-devel] [PATCH v2] Add remove_boot_device_path() function for hot-unplug device lijun
2014-05-11  9:17     ` Marcel Apfelbaum
2014-05-12 15:51       ` Jun Li
2014-05-14 13:36         ` Michael S. Tsirkin
2014-05-15 15:07 ` Michael S. Tsirkin
2014-05-17 12:09   ` Jun Li
2014-05-19  7:18     ` Markus Armbruster
2014-05-19 13:44       ` Jun Li [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=537A0AAE.2030902@gmail.com \
    --to=junmuzi@gmail.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=juli@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.