From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Hungyu Lin" <dennylin0707@gmail.com>, <zouyipeng@huawei.com>
Cc: <zhoujinghao24b@gmail.com>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <linux-pm@vger.kernel.org>,
<bpf@vger.kernel.org>
Subject: Re: [RFC PATCH] cpufreq: ext: serialize BPF registration with governor teardown
Date: Fri, 23 Oct 2026 16:04:18 +0000 [thread overview]
Message-ID: <DMCCFYFSY28Z.2BL8TJ1R2QZ1F@gmail.com> (raw)
In-Reply-To: <20261023083131.58291-1-dennylin0707@gmail.com>
On Fri, Oct 23, 2026 at 01:31 AM Hungyu Lin <dennylin0707@gmail.com> wrote:
> The 2025 fix addresses a separate policy-state lookup error. This
> teardown bug is present in the original, unmerged RFC as well.
Your bot is going nuts.
drivers/cpufreq/cpufreq_ext.c doesn't exist.
Stop sending slop. This is how you get blocked.
pw-bot: cr
next prev parent reply other threads:[~2026-10-23 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 10:13 [RFC PATCH 0/2] cpufreq_ext: Introduce cpufreq ext governor Yipeng Zou
2024-09-27 10:13 ` [RFC PATCH 1/2] " Yipeng Zou
2026-10-23 8:31 ` [RFC PATCH] cpufreq: ext: serialize BPF registration with governor teardown Hungyu Lin
2026-10-23 16:04 ` Alexei Starovoitov [this message]
2026-10-23 16:17 ` Hungyu Lin
2026-10-23 16:23 ` Alexei Starovoitov
2024-09-27 10:13 ` [RFC PATCH 2/2] cpufreq_ext: Add bpf sample Yipeng Zou
2024-09-29 16:56 ` [RFC PATCH 0/2] cpufreq_ext: Introduce cpufreq ext governor Alexei Starovoitov
2024-09-30 18:22 ` Tejun Heo
2024-09-29 23:23 ` Daniel Hodges
2025-09-18 12:52 ` [PATCH] cpufreq: ext: fix NULL deref in ext_gov_update() Jinghao Zhou
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=DMCCFYFSY28Z.2BL8TJ1R2QZ1F@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dennylin0707@gmail.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zhoujinghao24b@gmail.com \
--cc=zouyipeng@huawei.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