qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH] hw/mips/malta: Fix minor dead code issue
Date: Tue, 9 May 2023 17:37:18 +0200	[thread overview]
Message-ID: <5478a311-676e-6cfb-985e-15e0f2a24f20@linaro.org> (raw)
In-Reply-To: <CAFEAcA-2hrnjnMnA+GA1w0M-=rfcsO_FwJ2RkysMXpyCmCkO7g@mail.gmail.com>

On 9/5/23 15:07, Peter Maydell wrote:
> On Thu, 6 Apr 2023 at 16:54, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>>
>> On 6/4/23 17:37, Peter Maydell wrote:
>>> Coverity points out (in CID 1508390) that write_bootloader has
>>> some dead code, where we assign to 'p' and then in the following
>>> line assign to it again. This happened as a result of the
>>> refactoring in commit cd5066f8618b.
>>>
>>> Fix the dead code by removing the 'void *v' variable entirely and
>>> instead adding a cast when calling bl_setup_gt64120_jump_kernel(), as
>>> we do at its other callsite in write_bootloader_nanomips().
>>>
>>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>>> ---
>>>    hw/mips/malta.c | 5 +----
>>>    1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> 
> Are you planning to take this into a mips pullreq?
> If not, I can throw it into my next target-arm series.

I'll appreciate if you can take this single patch via your
arm tree. Thanks!



      reply	other threads:[~2023-05-09 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 15:37 [PATCH] hw/mips/malta: Fix minor dead code issue Peter Maydell
2023-04-06 15:54 ` Philippe Mathieu-Daudé
2023-05-09 13:07   ` Peter Maydell
2023-05-09 15:37     ` Philippe Mathieu-Daudé [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=5478a311-676e-6cfb-985e-15e0f2a24f20@linaro.org \
    --to=philmd@linaro.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=peter.maydell@linaro.org \
    --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).