From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Robert Lin <robelin@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
tglx@linutronix.de, pohsuns@nvidia.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
sumitg@nvidia.com
Subject: Re: [PATCH v7 0/3] clocksource: fix Tegra234 SoC Watchdog Timer.
Date: Fri, 2 May 2025 11:23:07 +0200 [thread overview]
Message-ID: <aBSO-wk5WPsWYs-V@mai.linaro.org> (raw)
In-Reply-To: <20250502043727.396896-1-robelin@nvidia.com>
On Fri, May 02, 2025 at 12:37:24PM +0800, Robert Lin wrote:
> From: robelin <robelin@nvidia.com>
>
> This set of patches includes a fix for watchdog for it may not bark
> due to self-pinging and adds WDIOC_GETTIMELEFT support.
>
> --
When sending a new version, could you please Cc: the watchdog maintainers ?
Thanks
-- Daniel
> V7:
> - Fix formatting
> - Consider overflow and warn if happens
>
> V6:
> - Fix timeleft value addition using unmatched time unit
> - Use u64 type to maintain the microseconds value in case of overflow
>
> V5:
> - Print warning message if get unexpected value from the register
>
> V4:
> - Improve the precision of timeleft value
> - Fix the unused variable warning
>
> V3:
> - Improve comment description
> - Refactor to fit codeline within 80 columns
> - Remove unused if(0) blocks
>
>
> V2:
> - Fix a compilation error, a warning and updates copyright
> --
[ ... ]
--
<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
prev parent reply other threads:[~2025-05-02 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 4:37 [PATCH v7 0/3] clocksource: fix Tegra234 SoC Watchdog Timer Robert Lin
2025-05-02 4:37 ` [PATCH v7 1/3] clocksource/drivers/timer-tegra186: add WDIOC_GETTIMELEFT support Robert Lin
2025-05-02 9:19 ` Daniel Lezcano
2025-05-02 10:16 ` Jon Hunter
2025-05-02 10:51 ` Daniel Lezcano
2025-05-02 11:06 ` Jon Hunter
2025-05-02 11:29 ` Daniel Lezcano
2025-05-02 12:37 ` Jon Hunter
2025-05-05 5:34 ` Robert Lin
2025-05-05 8:37 ` Daniel Lezcano
2025-05-05 5:34 ` Robert Lin
2025-05-02 4:37 ` [PATCH v7 2/3] clocksource/drivers/timer-tegra186: fix watchdog self-pinging Robert Lin
2025-05-02 4:37 ` [PATCH v7 3/3] clocksource/drivers/timer-tegra186: Remove unused bits Robert Lin
2025-05-02 9:23 ` Daniel Lezcano [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=aBSO-wk5WPsWYs-V@mai.linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pohsuns@nvidia.com \
--cc=robelin@nvidia.com \
--cc=sumitg@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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