From: Elena Afanasova <eafanasova@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, Ed Maste <emaste@freebsd.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Kamil Rytarowski <kamil@netbsd.org>,
Li-Wen Hsu <lwhsu@freebsd.org>, Brad <brad@comstyle.com>
Subject: Re: [PATCH v2] elfload: use g_new/g_malloc and g_autofree
Date: Tue, 06 Oct 2020 10:58:19 -0700 [thread overview]
Message-ID: <2e6c1f0c07c3ca06f99908fd3b776d791fb54771.camel@gmail.com> (raw)
In-Reply-To: <CAFEAcA-5FFqr1oUgjeym=NjaSfnZCgHz9UrsnwF6GjMmb+w+wg@mail.gmail.com>
Since bsd user space emulation doesn't work for me I can only use
'gmake check'... But some tests don't seem to be supported.
On Mon, 2020-10-05 at 10:55 +0100, Peter Maydell wrote:
> On Sun, 4 Oct 2020 at 13:22, Elena Afanasova <eafanasova@gmail.com>
> wrote:
> > Subject: [PATCH v2] elfload: use g_new/g_malloc and g_autofree
> >
> > Signed-off-by: Elena Afanasova <eafanasova@gmail.com>
> > ---
> > bsd-user/elfload.c | 79 ++++++++--------------------------------
> > ------
> > 1 file changed, 14 insertions(+), 65 deletions(-)
>
> Random question -- how are you testing this change? (bsd-user
> isn't covered by 'make check' I think).
>
> thanks
> -- PMM
prev parent reply other threads:[~2020-10-06 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 12:38 [PATCH] elfload: use g_new instead of malloc Elena Afanasova
2020-10-01 15:01 ` Thomas Huth
2020-10-02 5:05 ` Markus Armbruster
2020-10-02 5:18 ` Thomas Huth
2020-10-02 8:58 ` Markus Armbruster
2020-10-02 15:08 ` Eric Blake
2020-10-04 12:20 ` [PATCH v2] elfload: use g_new/g_malloc and g_autofree Elena Afanasova
2020-10-05 7:57 ` Markus Armbruster
2020-10-05 9:55 ` Peter Maydell
2020-10-06 17:58 ` Elena Afanasova [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=2e6c1f0c07c3ca06f99908fd3b776d791fb54771.camel@gmail.com \
--to=eafanasova@gmail.com \
--cc=armbru@redhat.com \
--cc=brad@comstyle.com \
--cc=emaste@freebsd.org \
--cc=kamil@netbsd.org \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
/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).