[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161026125658.25728-1-u.kleine-koenig@pengutronix.de>
Date: Wed, 26 Oct 2016 14:56:53 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Cc: kernel@...gutronix.de, Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>
Subject: [PATCH 0/5] print a hex number after a 0x prefix
Hello,
these were found by
git grep -i 0x%[lh]*[du]
Maybe it would make sense to catch this type of unconvenience in
checkpatch?
Best regards
Uwe
Uwe Kleine-König (5):
fs: exofs: print a hex number after a 0x prefix
block: DAC960: print a hex number after a 0x prefix
ipack: print a hex number after a 0x prefix
misc: sgi-gru: print a hex number after a 0x prefix
cris/arch-v32: cryptocop: print a hex number after a 0x prefix
arch/cris/arch-v32/drivers/cryptocop.c | 2 +-
drivers/block/DAC960.c | 4 ++--
drivers/ipack/ipack.c | 2 +-
drivers/misc/sgi-gru/grumain.c | 5 +++--
fs/exofs/dir.c | 2 +-
5 files changed, 8 insertions(+), 7 deletions(-)
--
2.9.3
Powered by blists - more mailing lists