Joel Stanley <j...@jms.id.au> writes:
> Users benefit from knowing which watchdog timer has expired. The address > of the watchdog's registers unambiguously indicates which has expired, > so log that. > > Reviewed-by: Cédric Le Goater <c...@kaod.org> > Signed-off-by: Joel Stanley <j...@jms.id.au> > --- > v2: Use HWADDR_PRIx > --- > hw/watchdog/wdt_aspeed.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/hw/watchdog/wdt_aspeed.c b/hw/watchdog/wdt_aspeed.c > index 145be6f99ce2..8787c5ad0f97 100644 > --- a/hw/watchdog/wdt_aspeed.c > +++ b/hw/watchdog/wdt_aspeed.c > @@ -219,7 +219,8 @@ static void aspeed_wdt_timer_expired(void *dev) > return; > } > > - qemu_log_mask(CPU_LOG_RESET, "Watchdog timer expired.\n"); > + qemu_log_mask(CPU_LOG_RESET, "Watchdog timer %" HWADDR_PRIx " > expired.\n", > + s->iomem.addr); nit: spacing off Reviewed-by: Alex Bennée <alex.ben...@linaro.org> > watchdog_perform_action(); > timer_del(s->timer); > } -- Alex Bennée
