On 31.08.21 11:29, Rasmus Villemoes wrote:
On 31/08/2021 10.17, Stefan Roese wrote:
Hi Rasmus,
I've pulled this patchset now into next [1] and have run it through
CI via Azure. Here an error occurs:
https://dev.azure.com/sr0718/u-boot/_build/results?buildId=109&view=logs&j=50449d1b-398e-53ae-4
On Tue, Aug 31, 2021 at 11:29:51AM +0200, Rasmus Villemoes wrote:
> On 31/08/2021 10.17, Stefan Roese wrote:
> > Hi Rasmus,
> >
> > I've pulled this patchset now into next [1] and have run it through
> > CI via Azure. Here an error occurs:
> >
> > https://dev.azure.com/sr0718/u-boot/_build/result
On 31/08/2021 10.17, Stefan Roese wrote:
> Hi Rasmus,
>
> I've pulled this patchset now into next [1] and have run it through
> CI via Azure. Here an error occurs:
>
> https://dev.azure.com/sr0718/u-boot/_build/results?buildId=109&view=logs&j=50449d1b-398e-53ae-48fa-6bf338edeb51&t=97605dd2-f5a5-5
Hi Rasmus,
I've pulled this patchset now into next [1] and have run it through
CI via Azure. Here an error occurs:
https://dev.azure.com/sr0718/u-boot/_build/results?buildId=109&view=logs&j=50449d1b-398e-53ae-48fa-6bf338edeb51&t=97605dd2-f5a5-5dd7-2118-315ffdc8bcd6&l=533
Could you please take a
Check that the watchdog_reset() implementation in wdt-uclass behaves
as expected:
- resets all activated watchdog devices
- leaves unactivated/stopped devices alone
- that the rate-limiting works, with a per-device threshold
Reviewed-by: Simon Glass
Reviewed-by: Stefan Roese
Signed-off-by: Rasm
5 matches
Mail list logo