[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161026125019.19bd9548ef2b64f6e38a3600@linux-foundation.org>
Date: Wed, 26 Oct 2016 12:50:19 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: linux-kernel@...r.kernel.org, kernel@...gutronix.de,
Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>,
Boaz Harrosh <ooo@...ctrozaur.com>,
Benny Halevy <bhalevy@...marydata.com>,
Samuel Iglesias Gonsalvez <siglesias@...lia.com>,
Jens Taprogge <jens.taprogge@...rogge.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dimitri Sivanich <sivanich@....com>,
Mikael Starvik <starvik@...s.com>,
Jesper Nilsson <jesper.nilsson@...s.com>
Subject: Re: [PATCH 0/5] print a hex number after a 0x prefix
On Wed, 26 Oct 2016 14:56:53 +0200 Uwe Kleine-K__nig <u.kleine-koenig@...gutronix.de> wrote:
> 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
um, lol, yup, thanks. I'll slam all five into 4.9-rcX.
Powered by blists - more mailing lists