All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>, <kernel@pengutronix.de>,
	Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH 4/5] misc: sgi-gru: print a hex number after a 0x prefix
Date: Wed, 26 Oct 2016 08:47:46 -0500	[thread overview]
Message-ID: <20161026134746.GA30169@sgi.com> (raw)
In-Reply-To: <20161026125658.25728-5-u.kleine-koenig@pengutronix.de>

On Wed, Oct 26, 2016 at 02:56:57PM +0200, Uwe Kleine-König wrote:
> It makes the result hard to interpret correctly if a base 10 number is
> prefixed by 0x. So change to a hex number.
>

Would like to have this be a decimal number.

Signed-off-by: Dimitri Sivanich <sivanich@sgi.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 1525870..33741ad 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 %d, 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);

  reply	other threads:[~2016-10-26 20:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 12:56 [PATCH 0/5] print a hex number after a 0x prefix Uwe Kleine-König
2016-10-26 12:56 ` [PATCH 1/5] fs: exofs: " Uwe Kleine-König
2016-10-26 12:56 ` [PATCH 2/5] block: DAC960: " Uwe Kleine-König
2016-10-26 12:56 ` [PATCH 3/5] ipack: " Uwe Kleine-König
2016-10-26 12:56 ` [PATCH 4/5] misc: sgi-gru: " Uwe Kleine-König
2016-10-26 13:47   ` Dimitri Sivanich [this message]
2016-10-27  6:05     ` Uwe Kleine-König
2016-10-26 12:56 ` [PATCH 5/5] cris/arch-v32: cryptocop: " Uwe Kleine-König
2016-10-26 19:50 ` [PATCH 0/5] " Andrew Morton
2016-10-26 23:35 ` Joe Perches
2016-10-27  6:51   ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161026134746.GA30169@sgi.com \
    --to=sivanich@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.