From: Gerd Hoffmann <kraxel@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix some coverity reported defects
Date: Tue, 05 Jan 2016 08:13:41 +0100 [thread overview]
Message-ID: <1451978021.31764.4.camel@redhat.com> (raw)
In-Reply-To: <1450861787-16213-1-git-send-email-bsd@redhat.com>
On Mi, 2015-12-23 at 14:39 +0530, Bandan Das wrote:
> The first change replaces QLIST_FOREACH with the safe variant
> and the second was incorrectly using MTPObject * in the trace function
> after freeing it.
>
> Bandan Das (2):
> usb-mtp: use safe variant when cleaning events list
> usb-mtp: fix call to trace function
>
> hw/usb/dev-mtp.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Added to usb patch queue.
thanks,
Gerd
prev parent reply other threads:[~2016-01-05 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 9:09 [Qemu-devel] [PATCH 0/2] Fix some coverity reported defects Bandan Das
2015-12-23 9:09 ` [Qemu-devel] [PATCH 1/2] usb-mtp: use safe variant when cleaning events list Bandan Das
2015-12-23 9:09 ` [Qemu-devel] [PATCH 2/2] usb-mtp: fix call to trace function Bandan Das
2016-01-05 7:13 ` Gerd Hoffmann [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=1451978021.31764.4.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=bsd@redhat.com \
--cc=pbonzini@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 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.