From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
devicetree@vger.kernel.org
Cc: tglx@linutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: timer: add Ralink SoCs timer
Date: Thu, 22 Jun 2023 11:59:45 +0200 [thread overview]
Message-ID: <6bc6a3f4-11d2-df4b-4631-96063e762667@linaro.org> (raw)
In-Reply-To: <20230620100231.1412582-1-sergio.paracuellos@gmail.com>
On 20/06/2023 12:02, 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
>
> diff --git a/Documentation/devicetree/bindings/timer/ralink,rt2880-timer.yaml b/Documentation/devicetree/bindings/timer/ralink,rt2880-timer.yaml
> new file mode 100644
> index 000000000000..daa7832babe3
> --- /dev/null
Applied, thanks
--
<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
prev parent reply other threads:[~2023-06-22 9:59 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
2023-06-22 6:47 ` Sergio Paracuellos
2023-06-22 9:59 ` Daniel Lezcano [this message]
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=6bc6a3f4-11d2-df4b-4631-96063e762667@linaro.org \
--to=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=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).