From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Alexey Charkov <alchark@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] dt-bindings: timer: via,vt8500-timer: Convert to YAML
Date: Wed, 14 May 2025 16:54:04 +0200 [thread overview]
Message-ID: <bdbf5357-beae-4e01-9a9e-f02d21f30eae@linaro.org> (raw)
In-Reply-To: <CABjd4YyQ1wg4Esd0ZGO-2+WGXkzrqfbhxLMWJ9N8eXTDr4BBgg@mail.gmail.com>
On 5/13/25 18:08, Alexey Charkov wrote:
> On Tue, May 13, 2025 at 7:49 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> On Tue, May 06, 2025 at 04:16:32PM +0400, Alexey Charkov wrote:
>>> Rewrite the textual description for the VIA/WonderMedia timer
>>> as YAML schema.
>>>
>>> The IP can generate up to four interrupts from four respective match
>>> registers, so reflect that in the schema.
>>>
>>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>>> Signed-off-by: Alexey Charkov <alchark@gmail.com>
>>> ---
>>> Changes in v3:
>>> - Added Rob's review tag (thanks Rob)
>>> - Rebased on top of next-20250506 to pull in MAINTAINERS updates
>>> - Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com
>>>
>>> Changes in v2:
>>> - split out this binding change from the big series affecting multiple
>>> subsystems unnecessarily (thanks Rob)
>>> - added description for the four possible interrupts (thanks Rob)
>>> - added overall description of the IC block
>>>
>>> Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/
>>> ---
>>
>> The patch does not apply.
>>
>> --- MAINTAINERS
>> +++ MAINTAINERS
>> @@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
>> F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt
>> F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml
>> F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml
>>
>> ^^^^^^ those bindings are not in my tree
>
> This series is based on next-20250506. Happy to rebase onto 6.15-rc1,
> but these will result in a (trivial) conflict when merging the
> different trees into -next and to master. Please let me know if that's
> better.
Usually the conflicts are solved from bottom to top when trees are pulled.
If I solve the conflict at my level, it is probable another conflict
will happen when the tree is pulled
Please rebase against v6.15-rc5
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-05-14 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 12:16 [PATCH v3] dt-bindings: timer: via,vt8500-timer: Convert to YAML Alexey Charkov
2025-05-13 15:49 ` Daniel Lezcano
2025-05-13 16:08 ` Alexey Charkov
2025-05-14 14:54 ` Daniel Lezcano [this message]
2025-05-14 15:14 ` Daniel Lezcano
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=bdbf5357-beae-4e01-9a9e-f02d21f30eae@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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).