From: Jiawen Liu <1298662399@qq.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: rtc-cadence: fix clock cleanup ordering
Date: Sun, 08 Nov 2026 21:22:12 +0400 [thread overview]
Message-ID: <tencent_78E495AE9F132060D92F62A55AFD53D11F06@qq.com> (raw)
In-Reply-To: <7739adcb-4234-4e28-a010-bcb64605b5af@wanadoo.fr>
Hi Christophe,
Thanks for the review and for adding Alexandre.
My description did not establish that the existing clock-disable order
causes a failure, so I should not have claimed that it leaves the clock
framework inconsistent.
I'll check the clock dependencies and the managed-clock option before
deciding whether a revised change is warranted. For any update, I'll use
get_maintainer.pl and prepare the patch with git format-patch.
Thanks,
Jiawen
prev parent reply other threads:[~2026-11-08 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 12:41 Jiawen Liu
2026-08-18 20:24 ` Christophe JAILLET
2026-11-08 17:22 ` Jiawen Liu [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=tencent_78E495AE9F132060D92F62A55AFD53D11F06@qq.com \
--to=1298662399@qq.com \
--cc=alexandre.belloni@bootlin.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linux-kernel@vger.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®