From: Peter Maydell <peter.maydell@linaro.org>
To: wliang@stu.xidian.edu.cn
Cc: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Fix a potential memory leak bug in write_boot_rom() (v6.2.0).
Date: Fri, 25 Feb 2022 11:37:38 +0000 [thread overview]
Message-ID: <CAFEAcA_8eRLK0eD9aHg65LeNa24+A9Z2D6cFdtUSSEJguOz_uQ@mail.gmail.com> (raw)
In-Reply-To: <74d28271.93a.17f2eee79db.Coremail.wliang@stu.xidian.edu.cn>
On Fri, 25 Feb 2022 at 03:33, <wliang@stu.xidian.edu.cn> wrote:
>
>
> >
> > yes. Could you please send a patch using g_autofree ?
> >
> > Thanks,
> >
> > C.
>
>
> Here is the new patch.
Hi; that patch doesn't seem to be using g_autofree. Did you attach the
wrong version of it?
You've sent a few patches recently, and they're all attachments
to the email. This is a bit awkward as our automatic tooling doesn't
handle attached patches -- it wants them inline in the email. For
a few one-off patches we can handle that at our end, but if you're
planning to send many more patches in future it might be worth trying
to sort out how to send them as non-attachments.
https://www.qemu.org/docs/master/devel/submitting-a-patch.html
has the details, including notes on using either git send-email
or the sourcehut service.
A couple more housekeeping type suggestions:
* please don't send new versions of patches as followups to
the email thread of the first patch; start a new thread
* subject lines should start with a prefix indicating what
part of the tree they apply to: in this case "hw/arm/aspeed".
This helps people scanning the email list to pick out patches
which they care about: from the function name alone it's
often hard to figure out which part of QEMU is involved
thanks
-- PMM
prev parent reply other threads:[~2022-02-25 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:39 Fix a potential memory leak bug in write_boot_rom() (v6.2.0) wliang
2022-02-23 16:15 ` Philippe Mathieu-Daudé
2022-02-24 8:10 ` Cédric Le Goater
2022-02-25 3:30 ` wliang
2022-02-25 11:37 ` Peter Maydell [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=CAFEAcA_8eRLK0eD9aHg65LeNa24+A9Z2D6cFdtUSSEJguOz_uQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=clg@kaod.org \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wliang@stu.xidian.edu.cn \
/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).