From: Eric Blake <eblake@redhat.com>
To: Matthias Weckbecker <matthias@weckbecker.name>,
Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] Fwd: [PATCH] QEMU patch for PCI handling bug (invalid free)
Date: Tue, 11 Dec 2018 08:24:34 -0600 [thread overview]
Message-ID: <1d51f9d6-7872-c1eb-cdd6-4db8134b859e@redhat.com> (raw)
In-Reply-To: <20181211072027.GA4465@weckbecker.name>
On 12/11/18 1:20 AM, Matthias Weckbecker wrote:
>> Maybe some of the explanation above should actually be moved to the
>> commit message of the patch itself?
>>
>
> yes, I agree. I have --amend'ed my commit message and re-attached it.
It's best to resend the patch as a new top-level thread with v2 in the
title; 'git send-email -v2' can do that.
More patch submission hints:
https://wiki.qemu.org/Contribute/SubmitAPatch
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-12-11 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 14:56 [Qemu-devel] Fwd: [PATCH] QEMU patch for PCI handling bug (invalid free) Kevin Wolf
2018-12-11 7:20 ` Matthias Weckbecker
2018-12-11 14:24 ` Eric Blake [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=1d51f9d6-7872-c1eb-cdd6-4db8134b859e@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=matthias@weckbecker.name \
--cc=mst@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).