linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Chen Gang <gang.chen@asianux.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	linux-m68k <linux-m68k@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arch/*/asm/include/bitops.h: api issue, find_*_bit() defination are different with each other
Date: Wed, 5 Jun 2013 15:02:22 +0200	[thread overview]
Message-ID: <20130605130222.GL23140@pengutronix.de> (raw)
In-Reply-To: <51AF225A.5020703@asianux.com>

Hello,

On Wed, Jun 05, 2013 at 07:34:50PM +0800, Chen Gang wrote:
> >> +extern unsigned long  _find_first_zero_bit_le(const void *p,
> > doesn't checkpatch critizise the double space in the line above?
> > 
> 
> Thank you very much for your carefully checking (could you tell me how
> do you find it ?)  :-)
I have no tool for that, it just catched my eye.

Best regards
Uwe

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

  reply	other threads:[~2013-06-05 13:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  1:10 [PATCH] arch/*/asm/include/bitops.h: api issue, find_*_bit() defination are different with each other Chen Gang
2013-06-05  1:11 ` Chen Gang
2013-06-05  1:13   ` [PATCH v2] " Chen Gang
2013-06-05  7:19     ` Uwe Kleine-König
2013-06-05 11:34       ` Chen Gang
2013-06-05 13:02         ` Uwe Kleine-König [this message]
2013-06-06  8:38           ` Chen Gang
2013-06-06  9:37         ` [PATCH v3] " Chen Gang
2013-06-18  3:33           ` Chen Gang
2013-07-05  1:09             ` Chen Gang

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=20130605130222.GL23140@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=gang.chen@asianux.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).