RE: [PATCH] watchdog: Correct watchdog timeout print message

2023-12-03 Thread Chanho Park
> -Original Message- > From: Stefan Roese > Sent: Friday, December 1, 2023 7:39 PM > To: Chanho Park ; u-boot@lists.denx.de > Subject: Re: [PATCH] watchdog: Correct watchdog timeout print message > > On 12/1/23 08:37, Stefan Roese wrote: > > On 11/27/23 02:05,

Re: [PATCH] watchdog: Correct watchdog timeout print message

2023-12-01 Thread Stefan Roese
On 12/1/23 08:37, Stefan Roese wrote: On 11/27/23 02:05, Chanho Park wrote: The wdt_start function takes timeout_ms as a parameter and starts the watchdog with this value. However, when you output the message, it shows the default timeout value for the watchdog device. So this patch fixes that p

Re: [PATCH] watchdog: Correct watchdog timeout print message

2023-11-30 Thread Stefan Roese
On 11/27/23 02:05, Chanho Park wrote: The wdt_start function takes timeout_ms as a parameter and starts the watchdog with this value. However, when you output the message, it shows the default timeout value for the watchdog device. So this patch fixes that part to output the correct timeout value

Re: [PATCH] watchdog: Correct watchdog timeout print message

2023-11-29 Thread Simon Glass
On Sun, 26 Nov 2023 at 18:06, Chanho Park wrote: > > The wdt_start function takes timeout_ms as a parameter and starts the > watchdog with this value. However, when you output the message, it shows > the default timeout value for the watchdog device. > So this patch fixes that part to output the c

[PATCH] watchdog: Correct watchdog timeout print message

2023-11-26 Thread Chanho Park
The wdt_start function takes timeout_ms as a parameter and starts the watchdog with this value. However, when you output the message, it shows the default timeout value for the watchdog device. So this patch fixes that part to output the correct timeout value. Before --> StarFive # wdt start 3000