From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, qemu-ppc@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-trivial] [PATCH] target-ppc: Fix compiler warning
Date: Sat, 21 Jun 2014 16:39:59 +0400 [thread overview]
Message-ID: <53A57D1F.9010604@msgid.tls.msk.ru> (raw)
In-Reply-To: <1403025508-19171-1-git-send-email-sw@weilnetz.de>
17.06.2014 21:18, Stefan Weil wrote:
> gcc reports a warning which is usually wrong:
[]
> Using g_assert_not_reached better documents the intention and does not
> have these problems.
Applied to -trivial, thanks!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, qemu-ppc@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] target-ppc: Fix compiler warning
Date: Sat, 21 Jun 2014 16:39:59 +0400 [thread overview]
Message-ID: <53A57D1F.9010604@msgid.tls.msk.ru> (raw)
In-Reply-To: <1403025508-19171-1-git-send-email-sw@weilnetz.de>
17.06.2014 21:18, Stefan Weil wrote:
> gcc reports a warning which is usually wrong:
[]
> Using g_assert_not_reached better documents the intention and does not
> have these problems.
Applied to -trivial, thanks!
/mjt
next prev parent reply other threads:[~2014-06-21 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 17:18 [Qemu-trivial] [PATCH] target-ppc: Fix compiler warning Stefan Weil
2014-06-17 17:18 ` [Qemu-devel] " Stefan Weil
2014-06-17 19:40 ` [Qemu-trivial] " Alexander Graf
2014-06-17 19:40 ` [Qemu-devel] " Alexander Graf
2014-06-21 12:39 ` Michael Tokarev [this message]
2014-06-21 12:39 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=53A57D1F.9010604@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.