Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: Roy Kollen Svendsen <roy.kollen.svendsen@akersolutions.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Julien Corjon <corjon.j@ecagroup.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2022.08.x] package/qt5base: fix memory leak
Date: Sun, 14 Jul 2024 17:51:32 +0200	[thread overview]
Message-ID: <20240714175132.48fbbace@windsurf> (raw)
In-Reply-To: <20231130160710.3146545-1-roy.kollen.svendsen@akersolutions.com>

Hello Roy,

On Thu, 30 Nov 2023 17:07:09 +0100
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:

> We noticed that our qt5 application froze after running for
> a few days on our imx8m mini based panel-pc.

Sorry for the very long delay in getting back to you. Unfortunately,
2022.08.x is no longer maintained, it was not even a LTS. I checked,
and all 4 commits you proposed to backport are part of the qt5base
version we have in 2024.02.x, so the currently maintained LTS branch is
not affected by this issue.

Therefore, I have marked your patch as Not Applicable in patchwork, as
we're no longer taking patches against 2022.08.x.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-14 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 16:07 [Buildroot] [PATCH 2022.08.x] package/qt5base: fix memory leak Roy Kollen Svendsen
2024-07-14 15:51 ` Thomas Petazzoni via buildroot [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=20240714175132.48fbbace@windsurf \
    --to=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=roy.kollen.svendsen@akersolutions.com \
    --cc=roykollensvendsen@gmail.com \
    --cc=thomas.petazzoni@bootlin.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