Re: [TRIVIAL PATCH] sgi-gru: Correct misuse of %0x<decimal>

[Dimitri Sivanich <sivanich@sgi.com>]

This should be %d, not 0x%x.

Nacked-by: Dimitri Sivanich <sivanich@sgi.com>

On Sun, Aug 02, 2015 at 01:27:27PM -0700, Joe Perches wrote:
> Correct misuse of 0x%d in logging message.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  drivers/misc/sgi-gru/grumain.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/misc/sgi-gru/grumain.c b/drivers/misc/sgi-gru/grumain.c
> index ae16c8c..a1ce324 100644
> --- a/drivers/misc/sgi-gru/grumain.c
> +++ b/drivers/misc/sgi-gru/grumain.c
> @@ -283,7 +283,7 @@ static void gru_unload_mm_tracker(struct gru_state *gru,
>         spin_lock(&gru->gs_asid_lock);
>         BUG_ON((asids->mt_ctxbitmap & ctxbitmap) != ctxbitmap);
>         asids->mt_ctxbitmap ^= ctxbitmap;
> -       gru_dbg(grudev, "gid %d, gts %p, gms %p, ctxnum 0x%d, asidmap 0x%lx\n",
> +       gru_dbg(grudev, "gid %d, gts %p, gms %p, ctxnum 0x%x, asidmap 0x%lx\n",
>                 gru->gs_gid, gts, gms, gts->ts_ctxnum, gms->ms_asidmap[0]);
>         spin_unlock(&gru->gs_asid_lock);
>         spin_unlock(&gms->ms_asid_lock);