From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] e1000: Fix spelling (segmentaion -> segmentation) in debug output
Date: Fri, 20 Apr 2012 13:22:22 +0100 [thread overview]
Message-ID: <20120420122222.GA13447@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1334726914-27870-1-git-send-email-sw@weilnetz.de>
On Wed, Apr 18, 2012 at 07:28:34AM +0200, Stefan Weil wrote:
> This was reported by https://bugs.launchpad.net/qemu/+bug/984476.
>
> I also changed the case for 'error'.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> hw/e1000.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks, applied to the trivial patches tree:
https://github.com/stefanha/qemu/commits/trivial-patches
Stefan
prev parent reply other threads:[~2012-04-20 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 5:28 [Qemu-trivial] [PATCH] e1000: Fix spelling (segmentaion -> segmentation) in debug output Stefan Weil
2012-04-20 12:22 ` Stefan Hajnoczi [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=20120420122222.GA13447@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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).