All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hector Martin <marcan@marcan.st>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Sven Peter <sven@svenpeter.dev>,
	Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Marc Zyngier <maz@kernel.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] MAINTAINERS: Add entries for Apple SoC cpufreq driver
Date: Wed, 4 May 2022 23:52:43 +0900	[thread overview]
Message-ID: <e0445aa6-0c96-b80d-154e-274be0c1a025@marcan.st> (raw)
In-Reply-To: <20220504101750.wmuicq3dytnxrw5o@vireshk-i7>

On 04/05/2022 19.17, Viresh Kumar wrote:
> On 04-05-22, 16:51, Hector Martin wrote:
>> Splitting this commit, as usual, to facilitate merges via the SoC tree.
>>
>> Signed-off-by: Hector Martin <marcan@marcan.st>
>> ---
>>  MAINTAINERS | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index edc96cdb85e8..39bfa478fe55 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1835,6 +1835,7 @@ T:	git https://github.com/AsahiLinux/linux.git
>>  F:	Documentation/devicetree/bindings/arm/apple.yaml
>>  F:	Documentation/devicetree/bindings/arm/apple/*
>>  F:	Documentation/devicetree/bindings/clock/apple,nco.yaml
>> +F:	Documentation/devicetree/bindings/cpufreq/apple,soc-cpufreq.yaml
>>  F:	Documentation/devicetree/bindings/i2c/apple,i2c.yaml
>>  F:	Documentation/devicetree/bindings/interrupt-controller/apple,*
>>  F:	Documentation/devicetree/bindings/mailbox/apple,mailbox.yaml
>> @@ -1844,6 +1845,7 @@ F:	Documentation/devicetree/bindings/power/apple*
>>  F:	Documentation/devicetree/bindings/watchdog/apple,wdt.yaml
>>  F:	arch/arm64/boot/dts/apple/
>>  F:	drivers/clk/clk-apple-nco.c
>> +F:	drivers/cpufreq/apple-soc-cpufreq.c
>>  F:	drivers/i2c/busses/i2c-pasemi-core.c
>>  F:	drivers/i2c/busses/i2c-pasemi-platform.c
>>  F:	drivers/irqchip/irq-apple-aic.c
> 
> This should be the last patch instead, or should at least be added
> after the files are merged first. If someone checks out at this
> commit, the files won't be available but still linked here.

Isn't that backwards? If someone touches the files, we want them to be
able to get_maintainer.pl, so the MAINTAINERS entries should come first.
It doesn't really cause any issues if there are entries that point at
files that don't exist yet, right?

Though this is mostly a moot point because the purpose of splitting this
out is so we can merge this one patch through the SoC tree, at which
point the ordering isn't guaranteed (unless the whole series goes
through SoC). It's a minor issue though; we've done it like this for
other series and it hasn't caused anyone trouble.

-- 
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub

WARNING: multiple messages have this Message-ID (diff)
From: Hector Martin <marcan@marcan.st>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Sven Peter <sven@svenpeter.dev>,
	 Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Marc Zyngier <maz@kernel.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] MAINTAINERS: Add entries for Apple SoC cpufreq driver
Date: Wed, 4 May 2022 23:52:43 +0900	[thread overview]
Message-ID: <e0445aa6-0c96-b80d-154e-274be0c1a025@marcan.st> (raw)
In-Reply-To: <20220504101750.wmuicq3dytnxrw5o@vireshk-i7>

On 04/05/2022 19.17, Viresh Kumar wrote:
> On 04-05-22, 16:51, Hector Martin wrote:
>> Splitting this commit, as usual, to facilitate merges via the SoC tree.
>>
>> Signed-off-by: Hector Martin <marcan@marcan.st>
>> ---
>>  MAINTAINERS | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index edc96cdb85e8..39bfa478fe55 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1835,6 +1835,7 @@ T:	git https://github.com/AsahiLinux/linux.git
>>  F:	Documentation/devicetree/bindings/arm/apple.yaml
>>  F:	Documentation/devicetree/bindings/arm/apple/*
>>  F:	Documentation/devicetree/bindings/clock/apple,nco.yaml
>> +F:	Documentation/devicetree/bindings/cpufreq/apple,soc-cpufreq.yaml
>>  F:	Documentation/devicetree/bindings/i2c/apple,i2c.yaml
>>  F:	Documentation/devicetree/bindings/interrupt-controller/apple,*
>>  F:	Documentation/devicetree/bindings/mailbox/apple,mailbox.yaml
>> @@ -1844,6 +1845,7 @@ F:	Documentation/devicetree/bindings/power/apple*
>>  F:	Documentation/devicetree/bindings/watchdog/apple,wdt.yaml
>>  F:	arch/arm64/boot/dts/apple/
>>  F:	drivers/clk/clk-apple-nco.c
>> +F:	drivers/cpufreq/apple-soc-cpufreq.c
>>  F:	drivers/i2c/busses/i2c-pasemi-core.c
>>  F:	drivers/i2c/busses/i2c-pasemi-platform.c
>>  F:	drivers/irqchip/irq-apple-aic.c
> 
> This should be the last patch instead, or should at least be added
> after the files are merged first. If someone checks out at this
> commit, the files won't be available but still linked here.

Isn't that backwards? If someone touches the files, we want them to be
able to get_maintainer.pl, so the MAINTAINERS entries should come first.
It doesn't really cause any issues if there are entries that point at
files that don't exist yet, right?

Though this is mostly a moot point because the purpose of splitting this
out is so we can merge this one patch through the SoC tree, at which
point the ordering isn't guaranteed (unless the whole series goes
through SoC). It's a minor issue though; we've done it like this for
other series and it hasn't caused anyone trouble.

-- 
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub

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

  reply	other threads:[~2022-05-04 14:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  7:51 [PATCH v2 0/4] Apple SoC cpufreq driver Hector Martin
2022-05-04  7:51 ` Hector Martin
2022-05-04  7:51 ` [PATCH v2 1/4] MAINTAINERS: Add entries for " Hector Martin
2022-05-04  7:51   ` Hector Martin
2022-05-04 10:17   ` Viresh Kumar
2022-05-04 10:17     ` Viresh Kumar
2022-05-04 14:52     ` Hector Martin [this message]
2022-05-04 14:52       ` Hector Martin
2022-05-05  8:42       ` Krzysztof Kozlowski
2022-05-05  8:42         ` Krzysztof Kozlowski
2022-05-05  8:44         ` Viresh Kumar
2022-05-05  8:44           ` Viresh Kumar
2022-05-04  7:51 ` [PATCH v2 2/4] dt-bindings: cpufreq: apple,soc-cpufreq: Add binding for Apple SoC cpufreq Hector Martin
2022-05-04  7:51   ` [PATCH v2 2/4] dt-bindings: cpufreq: apple, soc-cpufreq: " Hector Martin
2022-05-05  8:43   ` [PATCH v2 2/4] dt-bindings: cpufreq: apple,soc-cpufreq: " Krzysztof Kozlowski
2022-05-05  8:43     ` Krzysztof Kozlowski
2022-05-05 11:06     ` Hector Martin
2022-05-05 11:06       ` Hector Martin
2022-05-16 22:49   ` Rob Herring
2022-05-16 22:49     ` Rob Herring
2022-05-04  7:51 ` [PATCH v2 3/4] cpufreq: apple-soc: Add new driver to control Apple SoC CPU P-states Hector Martin
2022-05-04  7:51   ` Hector Martin
2022-05-04  7:51 ` [PATCH v2 4/4] arm64: dts: apple: Add CPU topology & cpufreq nodes for t8103 Hector Martin
2022-05-04  7:51   ` Hector Martin
2022-05-04 10:27 ` [PATCH v2 0/4] Apple SoC cpufreq driver Viresh Kumar
2022-05-04 10:27   ` Viresh Kumar
2022-05-04 16:00   ` Manivannan Sadhasivam
2022-05-04 16:00     ` Manivannan Sadhasivam
2022-05-08  7:16     ` Manivannan Sadhasivam
2022-05-08  7:16       ` Manivannan Sadhasivam

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=e0445aa6-0c96-b80d-154e-274be0c1a025@marcan.st \
    --to=marcan@marcan.st \
    --cc=alyssa@rosenzweig.io \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=maz@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sven@svenpeter.dev \
    --cc=ulf.hansson@linaro.org \
    --cc=viresh.kumar@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.