From: "Heiko Stübner" <heiko@sntech.de>
To: Chris Morgan <macromorgan@hotmail.com>
Cc: linux-rockchip@lists.infradead.org,
Chris Morgan <macroalpha82@gmail.com>,
devicetree@vger.kernel.org, shawn.lin@rock-chips.com,
diederik@cknow-tech.com, michael.riesch@collabora.com,
conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: timer: rockchip: Add rk3568 compatible
Date: Tue, 03 Nov 2026 20:08:51 +0100 [thread overview]
Message-ID: <2607835.uoxibFcf9D@diego> (raw)
In-Reply-To: <PH0PR19MB9973388CD960185681A4C3E16DA5692@PH0PR19MB997338.namprd19.prod.outlook.com>
Am Dienstag, 3. November 2026, 19:07:19 Mitteleuropäische Normalzeit schrieb Chris Morgan:
> On Tue, Nov 03, 2026 at 06:01:37PM +0100, Heiko Stübner wrote:
> > Hi Chris,
> >
> > Am Dienstag, 3. November 2026, 16:31:43 Mitteleuropäische Normalzeit schrieb Chris Morgan:
> > > From: Chris Morgan <macromorgan@hotmail.com>
> > >
> > > Add compatible string for Rockchip RK3568 timer.
> > >
> > > Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> > > ---
> > > Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml | 1 +
> >
> > Please make sure to check get_maintainers to catch all needed recipients.
> >
> > # scripts/get_maintainer.pl -f Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml
> >
> > you're especially missing the clocksource maintainers:
> > Daniel Lezcano <daniel.lezcano@kernel.org> (maintainer:CLOCKSOURCE, CLOCKEVENT DRIVERS,in file)
> > Thomas Gleixner <tglx@kernel.org> (maintainer:CLOCKSOURCE, CLOCKEVENT DRIVERS)
> >
> > and some additional lists:
> > linux-kernel@vger.kernel.org (open list:CLOCKSOURCE, CLOCKEVENT DRIVERS)
> > linux-arm-kernel@lists.infradead.org (moderated list:ARM/Rockchip SoC support)
> >
> > the clocksource part does not seem to have a dedicated list, so
> > linux-kernel should be included.
> >
> >
> > Heiko
> >
> >
>
> I apologize, sorry about that. I assumed since I was only modifying the
> device-tree and bindings I didn't need to copy the rest of the teams.
>
> Should I resubmit with the additional names?
very likely ... i.e. the binding is generally going through the driver-tree
here the tree holding the clocksource drivers.
For me to apply the binding, I'd definitly need an Ack from the clocksource
people.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-11-03 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 15:31 [PATCH 0/2] Add rockchip-timer for RK356X Chris Morgan
2026-11-03 15:31 ` [PATCH 1/2] dt-bindings: timer: rockchip: Add rk3568 compatible Chris Morgan
2026-11-03 17:01 ` Heiko Stübner
2026-11-03 18:07 ` Chris Morgan
2026-11-03 19:08 ` Heiko Stübner [this message]
2026-11-03 15:31 ` [PATCH 2/2] arm64: dts: rockchip: Add timer node for rk356x Chris Morgan
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 19:23 [PATCH 0/2] Add rockchip-timer for RK356X Chris Morgan
2026-11-03 19:23 ` [PATCH 1/2] dt-bindings: timer: rockchip: Add rk3568 compatible Chris Morgan
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=2607835.uoxibFcf9D@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=michael.riesch@collabora.com \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
/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