From: Michael Tokarev <mjt@tls.msk.ru>
To: Viswesh <visweshn92@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, kbastian@mail.uni-paderborn.de,
aneesh.kumar@linux.vnet.ibm.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] Fix typos in comments
Date: Thu, 19 Mar 2015 11:32:15 +0300 [thread overview]
Message-ID: <550A898F.1040806@msgid.tls.msk.ru> (raw)
In-Reply-To: <1426603988-3541-1-git-send-email-visweshn92@gmail.com>
17.03.2015 17:53, Viswesh wrote:
> The commit message is changed per review comments of Peter Maydell.
> This should be good now.
Applied to -trivial, without the above comment. Actually it was enough
to send the first version, it's easy to fix up commit comment than to
resend single patches like this.
Thanks,
/mjt
prev parent reply other threads:[~2015-03-19 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 14:53 [Qemu-devel] [PATCH v2] Fix typos in comments Viswesh
2015-03-17 15:24 ` Eric Blake
2015-03-19 8:32 ` Michael Tokarev [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=550A898F.1040806@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=visweshn92@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).