All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jia He <hejianet@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Joe Perches <joe@perches.com>
Subject: Re: [PATCHv2] staging: rtl8188eu: Fix coding style space related ERROR  problems
Date: Wed, 29 Oct 2014 16:45:28 +0800	[thread overview]
Message-ID: <20141029084528.GA18649@kroah.com> (raw)
In-Reply-To: <1413257312-9211-1-git-send-email-hejianet@gmail.com>

On Tue, Oct 14, 2014 at 11:28:32AM +0800, Jia He wrote:
> This fixes space related ERROR reports by checkpatch.pl
> Generated by $ git ls-files "drivers/staging/rtl8188eu/*.[ch]" | \
>   xargs ./scripts/checkpatch.pl -f --fix-inplace --strict --types=SPACING
> Already checked by text comparasion
> $git diff -w 
> and binary comparasion of r8188eu.ko
> $objdiff diff <old_commit> <new_commit>
> 
> Signed-off-by: Jia He <hejianet@gmail.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

This no longer applies to my tree due to the size of it and the fact
that others modified some of these files already.  Please refresh it
against my staging-testing branch of staging.git on git.kernel.org.

thanks,

greg k-h

  parent reply	other threads:[~2014-10-29 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  8:47 [PATCH] staging: rtl8188eu: Fix coding style space related ERROR problems Jia He
2014-10-13  9:13 ` Joe Perches
2014-10-14  3:28 ` [PATCHv2] " Jia He
2014-10-14  4:48   ` Jia He
2014-10-17  5:31   ` hejianet
2014-10-17  5:54     ` Dan Carpenter
2014-10-17  8:06     ` Greg Kroah-Hartman
2014-10-29  8:45   ` Greg Kroah-Hartman [this message]
2014-10-30 15:21   ` [PATCHv3] " Jia He
2014-10-30 15:29     ` Greg Kroah-Hartman
2014-11-03  4:47       ` hejianet
2014-10-31  2:07     ` [PATCH] " Jia He
2014-11-04  0:25       ` Greg Kroah-Hartman
2014-11-04  1:13         ` hejianet
2014-11-04  1:39   ` Jia He

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=20141029084528.GA18649@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=hejianet@gmail.com \
    --cc=joe@perches.com \
    --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.