From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Li Zhijian" <lizhijian@cn.fujitsu.com>,
fan.ni@samsung.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] hw/cxl: Fix CFMW config memory leak
Date: Tue, 8 Aug 2023 15:44:30 +0100 [thread overview]
Message-ID: <20230808154430.0000291e@Huawei.com> (raw)
In-Reply-To: <0adbfa43-719c-6d8e-9ec9-5d4a402be384@tls.msk.ru>
On Sat, 5 Aug 2023 08:46:29 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> 31.05.2023 14:08, Jonathan Cameron via wrote:
> > On Wed, 31 May 2023 09:51:43 +0200
> > Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> >
> >> On 31/5/23 08:07, Li Zhijian wrote:
> >>> Allocate targets and targets[n] resources when all sanity checks are
> >>> passed to avoid memory leaks.
> >>>
> >>> Suggested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> >>> ---
> >>> V3: allocte further resource when we can't fail # Philippe
> >>
> >> Thanks for the v3!
> >>
> >> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >
> > Thanks. I've added this near the top of my queue so will send
> > it out along with other similar fixes as a series for Michael
> > to consider picking up.
>
> Hi!
>
> Has this been forgotten? Is it still needed?
>
> /mjt
>
Sorry, I'm running a bit behind. Have this one a few other fixes
still queued up - I didn't consider any of them particularly critical
for the release so wasn't rushing.
I'll aim to get them out as a series soon though so they are
available for start of next cycle if not for slipping in before
the release.
Jonathan
next prev parent reply other threads:[~2023-08-08 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 6:07 [PATCH v3] hw/cxl: Fix CFMW config memory leak Li Zhijian
2023-05-31 7:51 ` Philippe Mathieu-Daudé
2023-05-31 11:08 ` Jonathan Cameron via
2023-08-05 5:46 ` Michael Tokarev
2023-08-08 14:44 ` Jonathan Cameron via [this message]
2023-09-08 17:02 ` Michael Tokarev
2023-09-11 9:18 ` Jonathan Cameron via
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=20230808154430.0000291e@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=fan.ni@samsung.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.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).