From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Patrice CHOTARD <patrice.chotard@foss.st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 4/4] ARM: dts: st: stih407: drop max-duty-cycle
Date: Mon, 25 Sep 2023 08:57:49 +0200 [thread overview]
Message-ID: <d08f6f17-f90c-4d71-a203-1d5365b5598a@linaro.org> (raw)
In-Reply-To: <b02d3983-c238-f79f-0edc-dd0db305b697@foss.st.com>
On 25/09/2023 08:50, Patrice CHOTARD wrote:
>
>
> On 9/24/23 20:53, Krzysztof Kozlowski wrote:
>> On 16/08/2023 08:54, Patrice CHOTARD wrote:
>>>
>>>
>>> On 7/30/23 19:49, Krzysztof Kozlowski wrote:
>>>> "max-duty-cycle" property was removed in the commit f747a1fe7848
>>>> ("regulator: pwm-regulator: Remove obsoleted property"):
>>>>
>>>> stih418-b2199.dtb: pwm-regulator: Unevaluated properties are not allowed ('max-duty-cycle' was unexpected)
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>>
>>>> ---
>>>>
>>>> Changes in v2:
>>>> 1. Correct subject prefix: AMR->ARM
>>>> ---
>>>> arch/arm/boot/dts/st/stih407-family.dtsi | 1 -
>>>> 1 file changed, 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm/boot/dts/st/stih407-family.dtsi b/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> index 3f58383a7b59..29302e74aa1d 100644
>>>> --- a/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> +++ b/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> @@ -111,7 +111,6 @@ pwm_regulator: pwm-regulator {
>>>> regulator-min-microvolt = <784000>;
>>>> regulator-max-microvolt = <1299000>;
>>>> regulator-always-on;
>>>> - max-duty-cycle = <255>;
>>>> status = "okay";
>>>> };
>>>>
>>>
>>>
>>> Applied on sti-next
>>
>> This is still not in linux-next (one month later!).
>
> Hi Krzysztof
>
> Yes i saw that, i submitted my pull request to ML but it hasn't be merged.
> I just notice i forgot to add soc@kernel.org in the sender list, my bad :-(
> I expect to resubmit it for v6.7.
So if you have them in your tree, why they are not in linux-next? Soc
has nothing to do with it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-25 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 17:49 [PATCH v2 1/4] ARM: dts: st: stm32mp157c-emstamp: drop incorrect vref_ddr property Krzysztof Kozlowski
2023-07-30 17:49 ` [PATCH v2 2/4] ARM: dts: st: stm32mp157c-emstamp: correct regulator-active-discharge Krzysztof Kozlowski
2023-08-10 15:47 ` Alexandre TORGUE
2023-07-30 17:49 ` [PATCH v2 3/4] ARM: dts: st: ste: switch to enable-gpios Krzysztof Kozlowski
2023-07-30 17:49 ` [PATCH v2 4/4] ARM: dts: st: stih407: drop max-duty-cycle Krzysztof Kozlowski
2023-08-04 15:38 ` Patrice CHOTARD
2023-08-16 6:54 ` Patrice CHOTARD
2023-09-24 18:53 ` Krzysztof Kozlowski
2023-09-25 6:50 ` Patrice CHOTARD
2023-09-25 6:57 ` Krzysztof Kozlowski [this message]
2023-08-10 15:47 ` [PATCH v2 1/4] ARM: dts: st: stm32mp157c-emstamp: drop incorrect vref_ddr property Alexandre TORGUE
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=d08f6f17-f90c-4d71-a203-1d5365b5598a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@foss.st.com \
--cc=robh+dt@kernel.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).