From: Stefan Hajnoczi <stefanha@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2] Fix copy&paste typos in documentation comments
Date: Fri, 24 Aug 2012 12:11:28 +0100 [thread overview]
Message-ID: <20120824111128.GG10867@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221717460.28960@mono>
On Wed, Aug 22, 2012 at 05:18:38PM +0200, BALATON Zoltan wrote:
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> memory.h | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> v2: indented memory_region_init_ram_ptr
Thanks, applied to the trivial patches tree:
https://github.com/stefanha/qemu/commits/trivial-patches
Stefan
next prev parent reply other threads:[~2012-08-24 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:18 [Qemu-devel] [PATCH v2] Fix copy&paste typos in documentation comments BALATON Zoltan
2012-08-24 11:11 ` Stefan Hajnoczi [this message]
2012-08-24 16:33 ` Andreas Färber
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=20120824111128.GG10867@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).