From: "Aleksandar Markovic" <Aleksandar.Markovic@rt-rk.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: arikalo@wavecomp.com, sw@weilnetz.de, qemu-devel@nongnu.org,
amarkovic@wavecomp.com
Subject: Re: [Qemu-devel] ?==?utf-8?q? ?==?utf-8?q? [PATCH for 4.1?==?utf-8?q? 3/4]?==?utf-8?q? target/mips: Add missing 'break' for certain cases of MFTR handling
Date: Fri, 12 Jul 2019 16:15:17 +0200 [thread overview]
Message-ID: <207b-5d289600-f-2bd63600@199222767> (raw)
In-Reply-To: <f8e07873-f5f9-218a-d542-daef5a1c1621@redhat.com>
> From: Philippe Mathieu-Daudé <philmd@redhat.com>
>
> > From: Aleksandar Markovic <amarkovic@wavecomp.com>
> >
> > This was found by GCC 8.3 static analysis.
> >
>
> Again, please amend:
>
> Fixes: ead9360e2fb
Who would think that this bug existed since 2007? ...étrange.
Thanks,
Aleksandar
next prev parent reply other threads:[~2019-07-12 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:37 [Qemu-devel] [PATCH for 4.1 0/4] target/mips: Fixes for 4.1 Aleksandar Markovic
2019-07-12 11:37 ` [Qemu-devel] [PATCH for 4.1 v2] linux-user: Fix structure target_ucontext for MIPS Aleksandar Markovic
2019-07-12 13:26 ` Laurent Vivier
2019-07-12 11:37 ` [Qemu-devel] [PATCH for 4.1 1/4] target/mips: Add 'fall through' comments for handling nanoMips' SHXS, SWXS Aleksandar Markovic
2019-07-12 11:37 ` [Qemu-devel] [PATCH for 4.1 2/4] target/mips: Add missing 'break' for a case of MTHC0 handling Aleksandar Markovic
2019-07-12 13:52 ` Philippe Mathieu-Daudé
2019-07-12 14:04 ` [Qemu-devel] ?==?utf-8?q? ?==?utf-8?q? [PATCH for 4.1?==?utf-8?q? 2/4]?==?utf-8?q? " Aleksandar Markovic
2019-07-12 11:37 ` [Qemu-devel] [PATCH for 4.1 3/4] target/mips: Add missing 'break' for certain cases of MFTR handling Aleksandar Markovic
2019-07-12 13:56 ` Philippe Mathieu-Daudé
2019-07-12 14:15 ` Aleksandar Markovic [this message]
2019-07-12 11:37 ` [Qemu-devel] [PATCH for 4.1 4/4] target/mips: Add missing 'break' for certain cases of MTTR handling Aleksandar Markovic
2019-07-12 13:58 ` Philippe Mathieu-Daudé
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=207b-5d289600-f-2bd63600@199222767 \
--to=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@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).