From: Paolo Bonzini <pbonzini@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SMM error in 2.4 changelog
Date: Wed, 11 Nov 2015 10:40:01 +0100 [thread overview]
Message-ID: <56430CF1.2020407@redhat.com> (raw)
In-Reply-To: <CAJ75kXY=2LkvHD7KiD0LAd92gBSp1P5uCy1mY77z3QpqLVeahw@mail.gmail.com>
On 10/11/2015 21:32, William Dauchy wrote:
> On Tue, Nov 3, 2015 at 10:01 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Yes, this is correct. Thanks!
>
> The mistake seems to be still present in changelog.
Fixed now, thanks for reminding.
Paolo
prev parent reply other threads:[~2015-11-11 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 22:26 [Qemu-devel] SMM error in 2.4 changelog William Dauchy
2015-11-03 9:01 ` Paolo Bonzini
2015-11-10 20:32 ` William Dauchy
2015-11-11 9:40 ` Paolo Bonzini [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=56430CF1.2020407@redhat.com \
--to=pbonzini@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wdauchy@gmail.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 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).