Fundamentals 2 min read

Why Linus Demanded a Name Change for the Mysterious 'GenPD' Kernel Subsystem

Linus Torvalds criticized the ambiguous 'GenPD' naming in a recent ARM SoC driver update PR for Linux 6.6, demanding the subsystem be renamed before merging after finding no documentation for the generic power‑management domain provider.

Open Source Linux
Open Source Linux
Open Source Linux
Why Linus Demanded a Name Change for the Mysterious 'GenPD' Kernel Subsystem

Linus Torvalds erupted over the cryptic abbreviation "GenPD" when a pull request titled "ARM: SoC/genpd driver updates for v6.6" was submitted to the Linux kernel.

The GenPD provider interface appears in several places within the kernel, yet no documentation explains its purpose.

Linus fetched the PR locally to investigate, but could only locate a vague entry in the MAINTAINERS file—"GENERIC PM DOMAIN PROVIDERS"—and an undocumented Kconfig option PM_GENERIC_DOMAINS, offering no clarification.

Concluding that "genpd" was a meaningless, unexplained name, Linus initially refused to merge the change, warning against using random, opaque identifiers.

Ultimately, he accepted the PR on the condition that the contributor rename the subsystem before the Linux 6.6 merge window closed.

GenPD driver update
GenPD driver update

Related link: https://lore.kernel.org/lkml/[email protected]

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Kernelpower managementgenpdv6.6
Open Source Linux
Written by

Open Source Linux

Focused on sharing Linux/Unix content, covering fundamentals, system development, network programming, automation/operations, cloud computing, and related professional knowledge.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.