From: Linus Torvalds <torvalds@linux-foundation.org> To: Arnd Bergmann <arnd@arndb.de> Cc: Ulf Hansson <ulf.hansson@linaro.org>, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>, soc@kernel.org, linux-arm-kernel@lists.infradead.org, Sebastian Reichel <sebastian.reichel@collabora.com>, "Rafael J . Wysocki" <rafael@kernel.org> Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6 Date: Tue, 29 Aug 2023 18:19:56 -0700 [thread overview] Message-ID: <CAHk-=wi5Lh-NG_rvcx3Zyqd2Uhj76G4V73tWCFULhVzOU6e1xg@mail.gmail.com> (raw) In-Reply-To: <96bb0de0-06d9-46f8-b02f-dc924afff13c@app.fastmail.com> On Tue, 29 Aug 2023 at 17:48, Arnd Bergmann <arnd@arndb.de> wrote: > > How about moving it to drivers/power/domain/ instead? That sounds like a sensible name and would seem to fit logically with our existing tree structure quite well. > I don't think we can easily rename the interfaces that have been > in use for the past 12 years I actually think the interface names are much less of an issue, since anybody using them is presumably familiar with the naming. It was only with the directory structure that I reacted to it, because that kind of exposes the naming to people who definitely are *not* familiar with it (ie me, but presumably anybody else who sees the diffstats etc fly past). And yes, we have a number of other pretty obscure driver names in our tree (I end up having to remind myself what "ntb" and "hsi" etc mean), and I don't tend to love them either, but at least they tend to be industry / vendor names. Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org> To: Arnd Bergmann <arnd@arndb.de> Cc: Ulf Hansson <ulf.hansson@linaro.org>, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>, soc@kernel.org, linux-arm-kernel@lists.infradead.org, Sebastian Reichel <sebastian.reichel@collabora.com>, "Rafael J . Wysocki" <rafael@kernel.org> Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6 Date: Tue, 29 Aug 2023 18:19:56 -0700 [thread overview] Message-ID: <CAHk-=wi5Lh-NG_rvcx3Zyqd2Uhj76G4V73tWCFULhVzOU6e1xg@mail.gmail.com> (raw) In-Reply-To: <96bb0de0-06d9-46f8-b02f-dc924afff13c@app.fastmail.com> On Tue, 29 Aug 2023 at 17:48, Arnd Bergmann <arnd@arndb.de> wrote: > > How about moving it to drivers/power/domain/ instead? That sounds like a sensible name and would seem to fit logically with our existing tree structure quite well. > I don't think we can easily rename the interfaces that have been > in use for the past 12 years I actually think the interface names are much less of an issue, since anybody using them is presumably familiar with the naming. It was only with the directory structure that I reacted to it, because that kind of exposes the naming to people who definitely are *not* familiar with it (ie me, but presumably anybody else who sees the diffstats etc fly past). And yes, we have a number of other pretty obscure driver names in our tree (I end up having to remind myself what "ntb" and "hsi" etc mean), and I don't tend to love them either, but at least they tend to be industry / vendor names. 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 1:21 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 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 [this message] 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-=wi5Lh-NG_rvcx3Zyqd2Uhj76G4V73tWCFULhVzOU6e1xg@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=rafael@kernel.org \ --cc=sebastian.reichel@collabora.com \ --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: linkBe 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.