From: Andrew Morton <akpm@linux-foundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Boaz Harrosh <ooo@electrozaur.com>,
Benny Halevy <bhalevy@primarydata.com>,
Samuel Iglesias Gonsalvez <siglesias@igalia.com>,
Jens Taprogge <jens.taprogge@taprogge.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dimitri Sivanich <sivanich@sgi.com>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [PATCH 0/5] print a hex number after a 0x prefix
Date: Wed, 26 Oct 2016 12:50:19 -0700 [thread overview]
Message-ID: <20161026125019.19bd9548ef2b64f6e38a3600@linux-foundation.org> (raw)
In-Reply-To: <20161026125658.25728-1-u.kleine-koenig@pengutronix.de>
On Wed, 26 Oct 2016 14:56:53 +0200 Uwe Kleine-K__nig <u.kleine-koenig@pengutronix.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.
next prev parent reply other threads:[~2016-10-26 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:56 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 ` Andrew Morton [this message]
2016-10-26 23:35 ` [PATCH 0/5] " 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=20161026125019.19bd9548ef2b64f6e38a3600@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=bhalevy@primarydata.com \
--cc=gregkh@linuxfoundation.org \
--cc=jens.taprogge@taprogge.org \
--cc=jesper.nilsson@axis.com \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=siglesias@igalia.com \
--cc=sivanich@sgi.com \
--cc=starvik@axis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®