All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Ray Jui <rjui@broadcom.com>,
	devicetree@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Rob Herring <robh+dt@kernel.org>,
	Scott Branden <sbranden@broadcom.com>
Subject: Re: [PATCH] dt-bindings: timer: brcm,kona-timer: convert to YAML
Date: Thu, 27 Apr 2023 09:59:11 -0700	[thread overview]
Message-ID: <d2edbd36-df75-92be-e247-507c82124505@gmail.com> (raw)
In-Reply-To: <168261469911.3163242.999660035852888472.robh@kernel.org>

On 4/27/23 09:58, Rob Herring wrote:
> 
> On Wed, 26 Apr 2023 20:28:54 +0200, Stanislav Jakubek wrote:
>> Convert Broadcom Kona family timer bindings to DT schema.
>>
>> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
>> ---
>>   .../bindings/timer/brcm,kona-timer.txt        | 25 ---------
>>   .../bindings/timer/brcm,kona-timer.yaml       | 55 +++++++++++++++++++
>>   2 files changed, 55 insertions(+), 25 deletions(-)
>>   delete mode 100644 Documentation/devicetree/bindings/timer/brcm,kona-timer.txt
>>   create mode 100644 Documentation/devicetree/bindings/timer/brcm,kona-timer.yaml
>>
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
> 
Rob, do you want me to take this patch, or will you take it via the DT tree?
-- 
Florian


      reply	other threads:[~2023-04-27 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 18:28 [PATCH] dt-bindings: timer: brcm,kona-timer: convert to YAML Stanislav Jakubek
2023-04-27 16:58 ` Rob Herring
2023-04-27 16:59   ` Florian Fainelli [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=d2edbd36-df75-92be-e247-507c82124505@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stano.jakubek@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 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.