All of lore.kernel.org
 help / color / mirror / Atom feed
From: <markus.stockhausen@gmx.de>
To: "'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
	<tglx@linutronix.de>, <linux-kernel@vger.kernel.org>,
	<howels@allthatwemight.be>, <bjorn@mork.no>
Subject: AW: [PATCH 0/4] clocksource/drivers/timer-rtl-otto: enhancements
Date: Wed, 10 Sep 2025 23:15:04 +0200	[thread overview]
Message-ID: <094b01dc2297$fa9977c0$efcc6740$@gmx.de> (raw)
In-Reply-To: <cf020451-115a-471a-bba0-4152015e7173@linaro.org>

> Von: Daniel Lezcano <daniel.lezcano@linaro.org> 
> Gesendet: Mittwoch, 10. September 2025 22:54
> 
> > This series fixes some shortcomings of the Realtek Otto timer driver.
> > These became evident after switching to longterm kernel 6.12. Devices
> > were randomly rebooted by the watchdog.
>
> Applied, thanks

Thanks a lot.




      reply	other threads:[~2025-09-10 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04  8:03 [PATCH 0/4] clocksource/drivers/timer-rtl-otto: enhancements Markus Stockhausen
2025-08-04  8:03 ` [PATCH 1/4] clocksource/drivers/timer-rtl-otto: work around dying timers Markus Stockhausen
2025-09-10  9:02   ` Daniel Lezcano
2025-09-10 10:16     ` AW: " markus.stockhausen
2025-09-10 16:39       ` Daniel Lezcano
2025-09-10 18:16         ` AW: " markus.stockhausen
2025-09-10 20:53           ` Daniel Lezcano
2025-08-04  8:03 ` [PATCH 2/4] clocksource/drivers/timer-rtl-otto: drop set_counter function Markus Stockhausen
2025-08-04  8:03 ` [PATCH 3/4] clocksource/drivers/timer-rtl-otto: do not interfere with interrupts Markus Stockhausen
2025-08-04  8:03 ` [PATCH 4/4] clocksource/drivers/timer-rtl-otto: simplify documentation Markus Stockhausen
2025-09-10 20:54 ` [PATCH 0/4] clocksource/drivers/timer-rtl-otto: enhancements Daniel Lezcano
2025-09-10 21:15   ` markus.stockhausen [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='094b01dc2297$fa9977c0$efcc6740$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=bjorn@mork.no \
    --cc=daniel.lezcano@linaro.org \
    --cc=howels@allthatwemight.be \
    --cc=linux-kernel@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.