All of lore.kernel.org
 help / color / mirror / Atom feed
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:31:59 -0700	[thread overview]
Message-ID: <CAHk-=wjLO=Jsdk2prq0piznMMCk+V0_fRaFRHEPuaALpF8J=hw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wg0gc4Cc90OL29Vr5gDtd4mnsKD+TxtoNtQbAryaWHkZQ@mail.gmail.com>

On Tue, 29 Aug 2023 at 17:18, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Please don't use random letter combinations that have absolutely
> no meaning to anybody else, and that aren't even explained.

Side note: at least to me, 'gen' is short for 'generate'. Looking at
existing kernel naming, that's how we've used it (lots of examples of
that from different areas).

Do we also have "generic"? Yes. And because 'gen' does not mean
'generic' to anybody, we've typically spelled it out - as in
asm-generic, but also 'sound/soc/generic', or in fact a _lot_ of other
examples.

Because we really aren't that close to running out of letters.

As to the 'pd' part, it actually has a fairly widely used meaning in
the industry, but it tends to be 'power delivery', in the USB-C sense.

So I really find that short-hand actively misleading,

I realize that the SoC code has used that shorthand internally, but
once you expose it like this, I really think you should do a much
better job at naming.

                 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:31:59 -0700	[thread overview]
Message-ID: <CAHk-=wjLO=Jsdk2prq0piznMMCk+V0_fRaFRHEPuaALpF8J=hw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wg0gc4Cc90OL29Vr5gDtd4mnsKD+TxtoNtQbAryaWHkZQ@mail.gmail.com>

On Tue, 29 Aug 2023 at 17:18, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Please don't use random letter combinations that have absolutely
> no meaning to anybody else, and that aren't even explained.

Side note: at least to me, 'gen' is short for 'generate'. Looking at
existing kernel naming, that's how we've used it (lots of examples of
that from different areas).

Do we also have "generic"? Yes. And because 'gen' does not mean
'generic' to anybody, we've typically spelled it out - as in
asm-generic, but also 'sound/soc/generic', or in fact a _lot_ of other
examples.

Because we really aren't that close to running out of letters.

As to the 'pd' part, it actually has a fairly widely used meaning in
the industry, but it tends to be 'power delivery', in the USB-C sense.

So I really find that short-hand actively misleading,

I realize that the SoC code has used that shorthand internally, but
once you expose it like this, I really think you should do a much
better job at naming.

                 Linus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-30  0:33 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
2023-08-30  0:18   ` Linus Torvalds
2023-08-30  0:31   ` Linus Torvalds [this message]
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-=wjLO=Jsdk2prq0piznMMCk+V0_fRaFRHEPuaALpF8J=hw@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.