From: Andreas Schwab <schwab@linux-m68k.org>
To: blauwirbel@gmail.com
Cc: blueswirl@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] Avoid GCC extension ?:
Date: Sun, 08 Jul 2012 14:09:52 +0200 [thread overview]
Message-ID: <m2liiusbcf.fsf@igel.home> (raw)
In-Reply-To: <5b88891d9683e0289cd8e24a999ac9d1fdb3fdb3.1341748181.git.blauwirbel@gmail.com> (blauwirbel@gmail.com's message of "Sun, 8 Jul 2012 11:51:26 +0000")
blauwirbel@gmail.com writes:
> + pstrcpy(bs->backing_format, sizeof(bs->backing_format),
> + backing_fmt ? backing_file : "");
s/backing_file/backing_fmt/
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-07-08 12:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 11:51 [Qemu-devel] [PATCH 0/5] portability patches blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 1/5] Avoid GCC extension ?: blauwirbel
2012-07-08 12:09 ` Andreas Schwab [this message]
2012-07-08 12:14 ` Blue Swirl
2012-07-11 12:54 ` Kevin Wolf
2012-07-11 13:09 ` Peter Maydell
2012-07-11 13:12 ` 陳韋任 (Wei-Ren Chen)
2012-07-12 20:34 ` Blue Swirl
2012-07-12 20:28 ` Blue Swirl
2012-07-12 21:08 ` Peter Maydell
2012-07-13 14:47 ` Blue Swirl
2012-07-13 9:05 ` Kevin Wolf
2012-07-13 14:58 ` Blue Swirl
2012-07-09 7:35 ` Markus Armbruster
2012-07-10 19:09 ` Blue Swirl
2012-07-08 11:51 ` [Qemu-devel] [PATCH 2/5] Avoid returning void blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 3/5] Use __asm__ instead of asm or __asm blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 4/5] Avoid unportable %m format blauwirbel
2012-07-10 20:53 ` Anthony Liguori
2012-07-10 21:12 ` Stefan Weil
2012-07-10 21:23 ` Anthony Liguori
2012-07-12 19:43 ` Blue Swirl
2012-07-08 11:51 ` [Qemu-devel] [PATCH 5/5] Avoid redefining inline blauwirbel
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=m2liiusbcf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=blauwirbel@gmail.com \
--cc=blueswirl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.