From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6
Date: Tue, 29 Aug 2023 17:18:59 -0700 [thread overview]
Message-ID: <CAHk-=wg0gc4Cc90OL29Vr5gDtd4mnsKD+TxtoNtQbAryaWHkZQ@mail.gmail.com> (raw)
In-Reply-To: <20230829213441.310655-1-ulf.hansson@linaro.org>
On Tue, 29 Aug 2023 at 14:34, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>
> Here's a pull-request that introduces the genpd provider subsystem.
I was starting to pull this, and then tried to figure out what the
heck "genpd" is.
Absolutely nothing in the pull request explains what it might be.
Even after actually pulling it, I couldn't really find anything useful.
The closest seems to be the MAINTAINERS file entry that says "GENERIC
PM DOMAIN PROVIDERS", which doesn't actually clarify anything.
Ok, so we have a Kconfig option for PM_GENERIC_DOMAINS, so I looked at
that. It has no help-text, as it is entirely an internal generated
one.
End result: I decided that without any kind of explanation at all,
"genpd" is a completely useless name, and that I don't want to
randomly add a new directory with zero explanation for what the heck
it is.
So I ended up unpulling it, because if I had to google what it is, I
wasn't going to pull it.
Can we please agree that
(a) five random letters in a row does not documentation make
(b) if we have a new subsystem, it should damn well have some
explanation for it
And even if you send me a new pull request with an actual explanation
for the term, do we really have to use such a horribly nasty name?
This is not some kind of industry standard shorthand.
Yes, google does find the term "genpd" having been used for a few
years in Linux SoC-land, but are we really so short on diskspace that
we can't use more descriptive names?
Now I look at this disaster area with no documentation, and realize
that it ends up also being part of Arnd's series of SoC pulls.
What a horrible thing this is. Please don't use random letter
combinations that have absolutely no meaning to anybody else, and that
aren't even explained.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6
Date: Tue, 29 Aug 2023 17:18:59 -0700 [thread overview]
Message-ID: <CAHk-=wg0gc4Cc90OL29Vr5gDtd4mnsKD+TxtoNtQbAryaWHkZQ@mail.gmail.com> (raw)
In-Reply-To: <20230829213441.310655-1-ulf.hansson@linaro.org>
On Tue, 29 Aug 2023 at 14:34, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>
> Here's a pull-request that introduces the genpd provider subsystem.
I was starting to pull this, and then tried to figure out what the
heck "genpd" is.
Absolutely nothing in the pull request explains what it might be.
Even after actually pulling it, I couldn't really find anything useful.
The closest seems to be the MAINTAINERS file entry that says "GENERIC
PM DOMAIN PROVIDERS", which doesn't actually clarify anything.
Ok, so we have a Kconfig option for PM_GENERIC_DOMAINS, so I looked at
that. It has no help-text, as it is entirely an internal generated
one.
End result: I decided that without any kind of explanation at all,
"genpd" is a completely useless name, and that I don't want to
randomly add a new directory with zero explanation for what the heck
it is.
So I ended up unpulling it, because if I had to google what it is, I
wasn't going to pull it.
Can we please agree that
(a) five random letters in a row does not documentation make
(b) if we have a new subsystem, it should damn well have some
explanation for it
And even if you send me a new pull request with an actual explanation
for the term, do we really have to use such a horribly nasty name?
This is not some kind of industry standard shorthand.
Yes, google does find the term "genpd" having been used for a few
years in Linux SoC-land, but are we really so short on diskspace that
we can't use more descriptive names?
Now I look at this disaster area with no documentation, and realize
that it ends up also being part of Arnd's series of SoC pulls.
What a horrible thing this is. Please don't use random letter
combinations that have absolutely no meaning to anybody else, and that
aren't even explained.
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-30 0:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 21:34 [GIT PULL] ARM: SoC/genpd driver updates for v6.6 Ulf Hansson
2023-08-29 21:34 ` Ulf Hansson
2023-08-30 0:18 ` Linus Torvalds [this message]
2023-08-30 0:18 ` Linus Torvalds
2023-08-30 0:31 ` Linus Torvalds
2023-08-30 0:31 ` Linus Torvalds
2023-08-30 0:47 ` Arnd Bergmann
2023-08-30 0:47 ` Arnd Bergmann
2023-08-30 1:19 ` Linus Torvalds
2023-08-30 1:19 ` Linus Torvalds
2023-08-30 8:33 ` Ulf Hansson
2023-08-30 8:33 ` Ulf Hansson
2023-08-30 15:07 ` Linus Torvalds
2023-08-30 15:07 ` Linus Torvalds
2023-08-31 0:08 ` Linus Torvalds
2023-08-31 0:08 ` Linus Torvalds
2023-08-31 11:29 ` Ulf Hansson
2023-08-31 11:29 ` Ulf Hansson
2023-08-31 9:32 ` Rafael J. Wysocki
2023-08-31 9:32 ` Rafael J. Wysocki
2023-08-31 11:37 ` Ulf Hansson
2023-08-31 11:37 ` Ulf Hansson
2023-08-31 12:58 ` Rafael J. Wysocki
2023-08-31 12:58 ` Rafael J. Wysocki
2023-09-11 7:52 ` Geert Uytterhoeven
2023-09-11 7:52 ` Geert Uytterhoeven
2023-09-11 11:28 ` Ulf Hansson
2023-09-11 11:28 ` Ulf Hansson
2023-09-11 11:48 ` Geert Uytterhoeven
2023-09-11 11:48 ` Geert Uytterhoeven
2023-09-11 12:06 ` Ulf Hansson
2023-09-11 12:06 ` Ulf Hansson
2023-09-11 13:06 ` Geert Uytterhoeven
2023-09-11 13:06 ` Geert Uytterhoeven
2023-09-11 13:57 ` Ulf Hansson
2023-09-11 13:57 ` Ulf Hansson
2023-09-12 13:57 ` Arnd Bergmann
2023-09-12 13:57 ` Arnd Bergmann
2023-09-12 22:19 ` Ulf Hansson
2023-09-12 22:19 ` Ulf Hansson
2023-08-31 0:10 ` pr-tracker-bot
2023-08-31 0:10 ` pr-tracker-bot
2023-09-26 21:03 ` patchwork-bot+linux-soc
2023-09-26 21:21 ` patchwork-bot+linux-soc
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='CAHk-=wg0gc4Cc90OL29Vr5gDtd4mnsKD+TxtoNtQbAryaWHkZQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.