From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>,
andersson@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: baolin.wang@linux.alibaba.com, florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Adding brcmstb-hwspinlock support
Date: Thu, 5 Mar 2026 20:59:17 +0100 [thread overview]
Message-ID: <38c0a23e-88cc-4f26-9648-fdeb9e99160f@kernel.org> (raw)
In-Reply-To: <CAKekbevZQBdvH5CCGyCDhs7ND6y65C=S3k1Aop8eh4CV5r_4aQ@mail.gmail.com>
On 05/03/2026 20:17, Kamal Dasu wrote:
>>
>> .../brcm,bcm7038-sun-top-ctrl-semaphore.yaml | 45 +++++++++
>> MAINTAINERS | 8 ++
>> drivers/hwspinlock/Kconfig | 11 ++-
>> drivers/hwspinlock/Makefile | 1 +
>> drivers/hwspinlock/brcmstb_hwspinlock.c | 96 +++++++++++++++++++
>> 5 files changed, 160 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,bcm7038-sun-top-ctrl-semaphore.yaml
>> create mode 100644 drivers/hwspinlock/brcmstb_hwspinlock.c
>>
>> --
>> 2.34.1
>>
>
> Hi Baolin, Rob,
>
> Gentle ping on this series. Patch 1/3 (dt-bindings) has been reviewed
> by Krzysztof and all previous review comments have been addressed.
Why pinging Rob? You got DT review. Or one review is not enough and you
need multiple maintainers engaged?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-05 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 22:04 Kamal Dasu
2026-02-24 22:04 ` [PATCH v6 1/3] dt-bindings: hwlock: " Kamal Dasu
2026-02-25 10:14 ` Krzysztof Kozlowski
2026-02-24 22:04 ` [PATCH v6 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2026-02-24 22:04 ` [PATCH v6 3/3] MAINTAINERS: adding entry for BRCMSTB HWSPINLOCK driver Kamal Dasu
2026-03-05 19:17 ` [PATCH v6 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2026-03-05 19:59 ` Krzysztof Kozlowski [this message]
2026-03-05 20:08 ` Kamal Dasu
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=38c0a23e-88cc-4f26-9648-fdeb9e99160f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®