From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
tglx@linutronix.de, robh+dt@kernel.org,
daniel.lezcano@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: timer: add Ralink SoCs timer
Date: Thu, 22 Jun 2023 08:16:08 +0200 [thread overview]
Message-ID: <50f75267-492f-d36b-f977-da2fb3a3fd1f@linaro.org> (raw)
In-Reply-To: <CAMhs-H_fUSnXHgO0ZXuGOX7gkuM98HXm+Y_jq1DxCv5Az=3Rag@mail.gmail.com>
On 22/06/2023 07:14, Sergio Paracuellos wrote:
> On Thu, Jun 22, 2023 at 3:51 AM Rob Herring <robh@kernel.org> wrote:
>>
>>
>> On Tue, 20 Jun 2023 12:02:31 +0200, Sergio Paracuellos wrote:
>>> Add YAML documentation for the timer which is present on Ralink SoCs.
>>>
>>> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
>>> ---
>>> Changes in v2:
>>> - Remove redundant 'documentation' word from subject.
>>> - Drop clock-names property.
>>>
>>> .../bindings/timer/ralink,rt2880-timer.yaml | 44 +++++++++++++++++++
>>> 1 file changed, 44 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/timer/ralink,rt2880-timer.yaml
>>>
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>>
>
> Thanks! Which tree is this supposed to go through?
Preferably clocksource/clockevents/timer drivers tree/
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-22 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:02 [PATCH v2] dt-bindings: timer: add Ralink SoCs timer Sergio Paracuellos
2023-06-22 1:51 ` Rob Herring
2023-06-22 5:14 ` Sergio Paracuellos
2023-06-22 6:16 ` Krzysztof Kozlowski [this message]
2023-06-22 6:47 ` Sergio Paracuellos
2023-06-22 9:59 ` 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=50f75267-492f-d36b-f977-da2fb3a3fd1f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--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).