From: Philipp Zabel <p.zabel@pengutronix.de>
To: Yu-Chun Lin <eleanor.lin@realtek.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
cylee12@realtek.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
james.tai@realtek.com, cy.huang@realtek.com,
stanley_chang@realtek.com
Subject: Re: [PATCH v16 0/3] reset: realtek: Add RTD1625 reset support
Date: Thu, 12 Nov 2026 10:41:09 +0100 [thread overview]
Message-ID: <1e434e5ab047b503e02e9ed9f3eb0aeb173d5602.camel@pengutronix.de> (raw)
In-Reply-To: <20261112053128.561149-1-eleanor.lin@realtek.com>
On Do, 2026-11-12 at 13:31 +0800, Yu-Chun Lin wrote:
> Hi all,
>
> This series adds reset controller support for the Realtek RTD1625 SoC.
>
> Since the reset and clock controllers share the same register space, they
> are now decoupled via the Auxiliary Bus framework. This allows the reset
> drivers to be submitted as a separate series.
>
> [...]
Applied to reset/next, thanks!
[1/3] dt-bindings: reset: Add Realtek RTD1625 reset IDs
https://git.kernel.org/pub/scm/linux/kernel/git/pza/linux.git/commit/?id=3b8e9b3eebd5
[2/3] reset: Add Realtek basic reset support
https://git.kernel.org/pub/scm/linux/kernel/git/pza/linux.git/commit/?id=9d125752e1a1
[3/3] reset: realtek: Add RTD1625 reset controller driver
https://git.kernel.org/pub/scm/linux/kernel/git/pza/linux.git/commit/?id=2716aec8c63a
regards
Philipp
prev parent reply other threads:[~2026-11-12 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 5:31 Yu-Chun Lin
2026-11-12 5:31 ` [PATCH v16 1/3] dt-bindings: reset: Add Realtek RTD1625 reset IDs Yu-Chun Lin
2026-11-12 9:08 ` Krzysztof Kozlowski
2026-11-12 9:10 ` Krzysztof Kozlowski
2026-11-12 5:31 ` [PATCH v16 2/3] reset: Add Realtek basic reset support Yu-Chun Lin
2026-11-12 5:31 ` [PATCH v16 3/3] reset: realtek: Add RTD1625 reset controller driver Yu-Chun Lin
2026-11-12 9:41 ` Philipp Zabel [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=1e434e5ab047b503e02e9ed9f3eb0aeb173d5602.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=cy.huang@realtek.com \
--cc=cylee12@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stanley_chang@realtek.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
all inboxes | Powered by JetHome®