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,
qemu-stable <qemu-stable@nongnu.org>,
"Michael Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3] hw/cxl: Fix CFMW config memory leak
Date: Mon, 11 Sep 2023 10:18:14 +0100 [thread overview]
Message-ID: <20230911101814.00006bda@Huawei.com> (raw)
In-Reply-To: <aa6e37b6-3bd9-5551-daf5-d040b926518e@tls.msk.ru>
On Fri, 8 Sep 2023 20:02:41 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> 08.08.2023 17:44, Jonathan Cameron:
>
> > 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.
>
> A month later, friendly ping? :)
> (this is sent to -stable too, fwiw).
https://lore.kernel.org/qemu-devel/20230904132806.6094-2-Jonathan.Cameron@huawei.com/
Posted a series with this in last week. Hopefully Michael will queue this
in his next pull.
Jonathan
>
> /mjt
>
>
prev parent reply other threads:[~2023-09-11 9:19 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
2023-09-08 17:02 ` Michael Tokarev
2023-09-11 9:18 ` Jonathan Cameron via [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=20230911101814.00006bda@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=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-stable@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).