linux-kernel - RE: [PATCH v4 0/3] clocksource: fix Tegra234 SoC Watchdog Timer.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <PH7PR12MB6418163E9BD4D9D94ECDBA5BD9BC2@PH7PR12MB6418.namprd12.prod.outlook.com>
Date: Thu, 17 Apr 2025 11:24:07 +0000
From: Robert Lin <robelin@...dia.com>
To: Jon Hunter <jonathanh@...dia.com>, "thierry.reding@...il.com"
	<thierry.reding@...il.com>, "daniel.lezcano@...aro.org"
	<daniel.lezcano@...aro.org>, "tglx@...utronix.de" <tglx@...utronix.de>,
	Pohsun Su <pohsuns@...dia.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, Sumit Gupta
	<sumitg@...dia.com>
Subject: RE: [PATCH v4 0/3] clocksource: fix Tegra234 SoC Watchdog Timer.

> -----Original Message-----
> From: Jon Hunter <jonathanh@...dia.com>
> Sent: Thursday, April 17, 2025 7:01 PM
> To: Robert Lin <robelin@...dia.com>; thierry.reding@...il.com;
> daniel.lezcano@...aro.org; tglx@...utronix.de; Pohsun Su
> <pohsuns@...dia.com>
> Cc: linux-kernel@...r.kernel.org; linux-tegra@...r.kernel.org; Sumit Gupta
> <sumitg@...dia.com>
> Subject: Re: [PATCH v4 0/3] clocksource: fix Tegra234 SoC Watchdog Timer.
> 
> 
> On 17/04/2025 10:31, Robert Lin wrote:
> > From: robelin <robelin@...dia.com>
> >
> > This set of patches includes a fix for watchdog for it may not bark
> > due to self-pinging and adds WDIOC_GETTIMELEFT support.
> >
> > --
> > V4:
> > - Improve the precision of timeleft value
> 
> I believe you also fixed the unused variable warning too!
> 


Right. Sorry for missing the description. I think I can improve this in patch v5, after Thierry's comments for other fixes that I need to do.

All the best,
Robert Lin