From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
shruthi.sanil@intel.com, tglx@linutronix.de, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com, mgross@linux.intel.com,
srikanth.thokala@intel.com,
lakshmi.bai.raja.subramanian@intel.com,
mallikarjunappa.sangannavar@intel.com
Subject: Re: [PATCH v10 1/2] dt-bindings: timer: Add bindings for Intel Keem Bay SoC Timer
Date: Wed, 30 Mar 2022 13:55:05 +0200 [thread overview]
Message-ID: <71e82477-16fb-2e7a-e5a9-e22327f31e77@kernel.org> (raw)
In-Reply-To: <7e711327-bcb8-4c7f-5537-425ba1a79e62@linaro.org>
On 30/03/2022 13:44, Daniel Lezcano wrote:
> On 22/03/2022 14:00, shruthi.sanil@intel.com wrote:
>> From: Shruthi Sanil <shruthi.sanil@intel.com>
>>
>> Add Device Tree bindings for the Timer IP, which can be used as
>> clocksource and clockevent device in the Intel Keem Bay SoC.
>>
>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>> Signed-off-by: Shruthi Sanil <shruthi.sanil@intel.com>
>
>
> In order to pick this binding I need an ack from Rob or Krzysztof (added
> to the recipients)
Rob was looking into this and there were some comments around v8, so I
will leave it to him.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-30 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:00 [PATCH v10 0/2] Add the driver for Intel Keem Bay SoC timer block shruthi.sanil
2022-03-22 13:00 ` [PATCH v10 1/2] dt-bindings: timer: Add bindings for Intel Keem Bay SoC Timer shruthi.sanil
2022-03-30 11:44 ` Daniel Lezcano
2022-03-30 11:55 ` Krzysztof Kozlowski [this message]
2022-04-06 8:06 ` Daniel Lezcano
2022-04-06 15:13 ` Rob Herring
2022-03-22 13:00 ` [PATCH v10 2/2] clocksource: Add Intel Keem Bay timer support shruthi.sanil
2022-03-30 5:04 ` [PATCH v10 0/2] Add the driver for Intel Keem Bay SoC timer block Sanil, Shruthi
2022-03-30 8:59 ` andriy.shevchenko
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=71e82477-16fb-2e7a-e5a9-e22327f31e77@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=shruthi.sanil@intel.com \
--cc=srikanth.thokala@intel.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