From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v2] clocksource/drivers/sh_cmt: Always leave device running after probe
Date: Tue, 18 Nov 2025 21:29:32 +0100 [thread overview]
Message-ID: <20251118202932.GE505486@fsdn.se> (raw)
In-Reply-To: <b80861d1-023d-4b07-9af0-a42e32e6d9ee@linaro.org>
On 2025-11-18 21:26:32 +0100, Daniel Lezcano wrote:
> On 11/18/25 21:18, Niklas Söderlund wrote:
>
> [ ... ]
>
> > Just wanted to check if you plan to take this patch in this cycle, no
> > rush. But I don't want to start trying similar fixes for TMU before we
> > have agreed on this one.
>
>
> Yes, I picked it up. It should be in linux-next
Yes, I see it now. Thanks and sorry for the noise.
>
>
> --
> <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
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2025-11-18 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:20 [PATCH v2] clocksource/drivers/sh_cmt: Always leave device running after probe Niklas Söderlund
2025-11-05 15:36 ` Daniel Lezcano
2025-11-05 16:06 ` Niklas Söderlund
2025-11-05 16:39 ` Daniel Lezcano
2025-11-05 18:32 ` Niklas Söderlund
2025-11-07 9:53 ` Daniel Lezcano
2025-11-09 14:37 ` Niklas Söderlund
2025-11-18 20:18 ` Niklas Söderlund
2025-11-18 20:26 ` Daniel Lezcano
2025-11-18 20:29 ` Niklas Söderlund [this message]
2025-11-18 20:30 ` Daniel Lezcano
2025-11-26 14:40 ` [tip: timers/clocksource] " tip-bot2 for Niklas Söderlund
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=20251118202932.GE505486@fsdn.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=daniel.lezcano@linaro.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.