From: Dmitry Antipov <dmantipov@yandex.ru>
To: Armin Wolf <W_Armin@gmx.de>, "Rafael J. Wysocki" <rafael@kernel.org>
Cc: robert.moore@intel.com, rafael.j.wysocki@intel.com,
lenb@kernel.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPICA: Fix memory leak then namespace lookup fails
Date: Fri, 12 Apr 2024 20:07:24 +0300 [thread overview]
Message-ID: <31236394-8211-4d93-81bd-ada9b039a2d4@yandex.ru> (raw)
In-Reply-To: <23c89f70-98d3-41a5-927c-ff4f2300ab7e@gmx.de>
On 4/12/24 19:16, Armin Wolf wrote:
> Dmitry, do you think that this memory leak is critical? If not, then i think
> we can wait till the next ACPICA release.
Hopefully not too critical. The leak itself is small, and it's highly depended
from the particular notebook model and/or UEFI BIOS revision, so it should be
safe to wait.
Dmitry
prev parent reply other threads:[~2024-04-12 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 0:47 [PATCH] ACPICA: Fix memory leak then namespace lookup fails Armin Wolf
2024-04-08 14:29 ` Rafael J. Wysocki
2024-04-12 16:16 ` Armin Wolf
2024-04-12 17:07 ` Dmitry Antipov [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=31236394-8211-4d93-81bd-ada9b039a2d4@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=W_Armin@gmx.de \
--cc=acpica-devel@lists.linux.dev \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).