linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ulf Hansson" <ulf.hansson@linaro.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.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>
Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6
Date: Tue, 12 Sep 2023 15:57:49 +0200	[thread overview]
Message-ID: <d1d6b2a2-8be1-4269-a504-5762b94df77a@app.fastmail.com> (raw)
In-Reply-To: <CAPDyKFpUUJeGD77GTYCk59cvW=SdGTkOEXH4dap1JQWekAa0Eg@mail.gmail.com>

On Mon, Sep 11, 2023, at 13:28, Ulf Hansson wrote:
> On Mon, 11 Sept 2023 at 09:52, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>
>> And I just realized you moved the code and Makefiles to drivers/genpd/,
>> but not the Kconfig symbols and logic, which still lives under
>> drivers/soc/.  So resolving that (and the name) is something that
>> should be resolved sooner rather than later...
>
> In regards to the name, I am relying on input from Linus to make a
> final decision before I send a patch. In regards to this, I have also
> started working on a documentation patch for genpd. It needs some more
> polishing before I can send it though.

I'm fairly sure that Linus was instead waiting for you to send
a patch or pull request for the rename. Please just pick a name
that you like and that Linus hasn't already objected to and send
it so the rename makes it into -rc2 for others to base on.

If anyone has objections to the new name, you'll find out about
it then, but I think we trust your judgement here.

     Arnd

  parent reply	other threads:[~2023-09-12 13:58 UTC|newest]

Thread overview: 20+ 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-30  0:18 ` Linus Torvalds
2023-08-30  0:31   ` Linus Torvalds
2023-08-30  0:47     ` Arnd Bergmann
2023-08-30  1:19       ` Linus Torvalds
2023-08-30  8:33         ` Ulf Hansson
2023-08-30 15:07           ` Linus Torvalds
2023-08-31  0:08             ` Linus Torvalds
2023-08-31 11:29               ` Ulf Hansson
2023-08-31  9:32           ` Rafael J. Wysocki
2023-08-31 11:37             ` Ulf Hansson
2023-08-31 12:58               ` Rafael J. Wysocki
2023-09-11  7:52               ` Geert Uytterhoeven
2023-09-11 11:28                 ` Ulf Hansson
2023-09-11 11:48                   ` Geert Uytterhoeven
2023-09-11 12:06                     ` Ulf Hansson
2023-09-11 13:06                       ` Geert Uytterhoeven
2023-09-11 13:57                         ` Ulf Hansson
2023-09-12 13:57                   ` Arnd Bergmann [this message]
2023-09-12 22:19                     ` Ulf Hansson

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=d1d6b2a2-8be1-4269-a504-5762b94df77a@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --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=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).