All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH 0/5] print a hex number after a 0x prefix
Date: Thu, 27 Oct 2016 08:51:29 +0200	[thread overview]
Message-ID: <20161027065129.b6k2lpuy55ktlhda@pengutronix.de> (raw)
In-Reply-To: <1477524922.1998.27.camel@perches.com>

On Wed, Oct 26, 2016 at 04:35:22PM -0700, Joe Perches wrote:
> On Wed, 2016-10-26 at 14:56 +0200, Uwe Kleine-König 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?
> 
> Already there.

Oh, you're right. It's there since over a year. Strange that noone fixed
this before then.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2016-10-27  6:51 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
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 [this message]

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=20161027065129.b6k2lpuy55ktlhda@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.