From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] clocksource/drivers/sh_cmt: Do not power down channels used for events
Date: Wed, 24 Sep 2025 15:43:24 +0200 [thread overview]
Message-ID: <69f09f55-fd2f-47a9-887a-e9c2cf7c21df@linaro.org> (raw)
In-Reply-To: <20250924093132.GA1062104@ragnatech.se>
On 24/09/2025 11:31, Niklas Söderlund wrote:
[ ... ]
> If it's not too late I think we should drop it. The issue this work
> tries to solve is a lockdep blurb which highlights a design issue in the
> driver. But the driver have function properly in the past. So I think
> it's better I work on solving the blurb without any regressions.
Ok, dropping 2/2 but keeping 1/2 is fine, right ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-09-24 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 14:26 [PATCH v2 0/2] clocksource/drivers/sh_cmt: Improve clock event design Niklas Söderlund
2025-09-10 14:26 ` [PATCH v2 1/2] clocksource/drivers/sh_cmt: Split start/stop of clock source and events Niklas Söderlund
2025-09-10 14:26 ` [PATCH v2 2/2] clocksource/drivers/sh_cmt: Do not power down channels used for events Niklas Söderlund
2025-09-23 14:56 ` Geert Uytterhoeven
2025-09-24 9:19 ` Daniel Lezcano
2025-09-24 9:31 ` Niklas Söderlund
2025-09-24 13:43 ` Daniel Lezcano [this message]
2025-09-24 13:46 ` Geert Uytterhoeven
2025-09-25 5:12 ` Niklas Söderlund
2025-09-17 9:02 ` [PATCH v2 0/2] clocksource/drivers/sh_cmt: Improve clock event design Daniel Lezcano
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=69f09f55-fd2f-47a9-887a-e9c2cf7c21df@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--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
all inboxes | Powered by JetHome®