From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
devel@acpica.org
Subject: Re: BUG: bisected: thermald regression (MEMLEAK) in commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
Date: Fri, 28 Oct 2022 20:25:14 +0200 [thread overview]
Message-ID: <CAJZ5v0jfHtOXDFUFYj8EOGMT74iWfkQqEW3L2D2dZv6Y1jFSrw@mail.gmail.com> (raw)
In-Reply-To: <a4457f46-72c9-f9b0-b87a-cb3dd5cd066f@alu.unizg.hr>
On Thu, Oct 27, 2022 at 8:20 PM Mirsad Goran Todorovac
<mirsad.todorovac@alu.unizg.hr> wrote:
>
> Re-sending compressed attachments to fit into the size limit.
>
> On 27. 10. 2022. 20:03, Mirsad Goran Todorovac wrote:
> > P.S.
> >
> > Forgot another useful thing you've mentioned: please find attached the
> > dmesg output.
> >
> > Good luck!
I'm wondering if the problem is reproducible with this patch applied:
https://patchwork.kernel.org/project/linux-acpi/patch/20221019073443.248215-1-chenzhongjin@huawei.com/
next prev parent reply other threads:[~2022-10-28 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e0f06714-5a49-a4e6-24e6-c4103c820819@alu.unizg.hr>
2022-10-24 15:51 ` BUG: bisected: thermald regression (MEMLEAK) in commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 srinivas pandruvada
2022-10-24 18:34 ` Mirsad Goran Todorovac
2022-10-24 18:39 ` srinivas pandruvada
2022-10-24 18:56 ` Mirsad Goran Todorovac
2022-10-26 17:52 ` Mirsad Goran Todorovac
2022-10-26 22:48 ` srinivas pandruvada
[not found] ` <78e347e9-c8b1-f228-ca32-0ad6186a6285@alu.unizg.hr>
2022-10-27 18:20 ` Mirsad Goran Todorovac
2022-10-28 18:25 ` Rafael J. Wysocki [this message]
2022-11-15 10:36 ` Thorsten Leemhuis
2022-11-15 11:17 ` Mirsad Goran Todorovac
2022-11-15 14:40 ` Mirsad Goran Todorovac
2022-11-15 14:49 ` Rafael J. Wysocki
2022-11-15 18:57 ` Mirsad Goran Todorovac
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=CAJZ5v0jfHtOXDFUFYj8EOGMT74iWfkQqEW3L2D2dZv6Y1jFSrw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
/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).