qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@freegeek.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] spelling typo (compatibilty) in hw/fw_cfg.c
Date: Sat, 13 Mar 2010 13:38:59 -0800	[thread overview]
Message-ID: <20100313213859.GF8032@claws.fglan> (raw)
In-Reply-To: <f43fc5581003130305x73e4866apccef71f5c3e4b739@mail.gmail.com>

On Sat, Mar 13, 2010 at 01:05:03PM +0200, Blue Swirl wrote:
> On 3/12/10, Vagrant Cascadian <vagrant@freegeek.org> wrote:
> > here's a trivial patch to fix the spelling of "compatibility":
> 
> Please add a Signed-off-by: line.

hope this is what you're looking for:

Signed-off-by: Vagrant Cascadian <vagrant@freegeek.org>

> >
> >  diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
> >  index fe6c543..22ebb50 100644
> >  --- a/hw/fw_cfg.c
> >  +++ b/hw/fw_cfg.c
> >  @@ -179,7 +179,7 @@ static int get_uint32_as_uint16(QEMUFile *f, void *pv, size_t size)
> >
> >   static void put_unused(QEMUFile *f, void *pv, size_t size)
> >   {
> >  -    fprintf(stderr, "uint32_as_uint16 is only used for backward compatibilty.\n");
> >  +    fprintf(stderr, "uint32_as_uint16 is only used for backward compatibility.\n");
> >      fprintf(stderr, "This functions shouldn't be called.\n");
> >   }

live well,
  vagrant

  parent reply	other threads:[~2010-03-13 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 18:26 [Qemu-devel] spelling typo (compatibilty) in hw/fw_cfg.c Vagrant Cascadian
2010-03-13 11:05 ` Blue Swirl
2010-03-13 21:38   ` [Qemu-devel] manpage errors Vagrant Cascadian
2010-03-14 10:14     ` [Qemu-devel] " Blue Swirl
2010-03-13 21:38   ` Vagrant Cascadian [this message]
2010-03-14  8:54     ` [Qemu-devel] spelling typo (compatibilty) in hw/fw_cfg.c Blue Swirl

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=20100313213859.GF8032@claws.fglan \
    --to=vagrant@freegeek.org \
    --cc=blauwirbel@gmail.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).