From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PULL 0/2] fw_cfg patches for 2020-07-21
Date: Thu, 23 Jul 2020 14:56:59 +0200 [thread overview]
Message-ID: <bde02d2a-e967-d80f-13ad-37c787d85a2c@redhat.com> (raw)
In-Reply-To: <CAFEAcA-H0E-EFkbHuVOhyy1_p47dbr5uHXqzZL=jgwXVzmD1vw@mail.gmail.com>
On 7/23/20 12:43 PM, Peter Maydell wrote:
> On Tue, 21 Jul 2020 at 18:54, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> The following changes since commit 90218a9a393c7925f330e7dcc08658e2a01d3bd4:
>>
>> Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2020-07=
>> -21' into staging (2020-07-21 10:24:38 +0100)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.com/philmd/qemu.git tags/fw_cfg-20200721
>>
>> for you to fetch changes up to 077195187b47d83418e5fb521c89d7881fab3049:
>>
>> hw/nvram/fw_cfg: Let fw_cfg_add_from_generator() return boolean value (2020=
>> -07-21 16:47:54 +0200)
>>
>> ----------------------------------------------------------------
>> fw_cfg patches
>>
>> Fixes the DEADCODE issue reported by Coverity (CID 1430396).
>>
>> CI jobs result:
>> . https://gitlab.com/philmd/qemu/-/pipelines/169086301
>>
>> ----------------------------------------------------------------
>>
>> Philippe Mathieu-Daud=C3=A9 (2):
>
> Something in your cover-letter creation is not handling UTF-8 right :-)
Yes, this is a known git-publish issue:
https://github.com/stefanha/git-publish/issues/88
It only happens with the cover, it doesn't affect the patches,
so it is considered a very low priority issue :)
>
>> hw/nvram/fw_cfg: Simplify fw_cfg_add_from_generator() error
>> propagation
>> hw/nvram/fw_cfg: Let fw_cfg_add_from_generator() return boolean value
>
>
> Applied, thanks.
>
> Please update the changelog at https://wiki.qemu.org/ChangeLog/5.1
> for any user-visible changes.
Thanks (no user-visible changes in these patches).
Phil.
prev parent reply other threads:[~2020-07-23 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:53 [PULL 0/2] fw_cfg patches for 2020-07-21 Philippe Mathieu-Daudé
2020-07-21 17:53 ` [PULL 1/2] hw/nvram/fw_cfg: Simplify fw_cfg_add_from_generator() error propagation Philippe Mathieu-Daudé
2020-07-21 17:53 ` [PULL 2/2] hw/nvram/fw_cfg: Let fw_cfg_add_from_generator() return boolean value Philippe Mathieu-Daudé
2020-07-23 10:43 ` [PULL 0/2] fw_cfg patches for 2020-07-21 Peter Maydell
2020-07-23 12:56 ` 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=bde02d2a-e967-d80f-13ad-37c787d85a2c@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.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).