public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: pmarzo <marzo.pedro@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	gregkh@linuxfoundation.org, navyasri.tech@gmail.com,
	dilekuzulmez@gmail.com, haticeerturk27@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Staging: rtl8192u: Fix coding style issues at ieee80211_crypt_wep.c
Date: Mon, 18 May 2015 13:30:13 -0700	[thread overview]
Message-ID: <1431981013.2870.82.camel@perches.com> (raw)
In-Reply-To: <1431988532.9328.27.camel@pedrito-laptop>

On Tue, 2015-05-19 at 00:35 +0200, pmarzo wrote:
> On Mon, 2015-05-18 at 13:04 -0700, Joe Perches wrote:
> > btw: using:
> > 
> > $ ./scripts/checkpatch.pl -f --strict --fix-inplace \
> >    --types=spacing,space_before_tab,pointer_location,trailing_whitespace,bracket_space,space_before_tab,indented_label,parenthesis_alignment \
> >    $file
> > 
> Nice to see a script programs far better than me :-(

Nah...

The script is a stupid little tool.  People like you are
much better at making actually useful improvements to code.



  reply	other threads:[~2015-05-18 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 17:36 [PATCH v2] Staging: rtl8192u: Fix coding style issues at ieee80211_crypt_wep.c Pedro Marzo Perez
2015-05-18 16:15 ` Dan Carpenter
2015-05-18 21:56   ` pmarzo
2015-05-18 20:04     ` Joe Perches
2015-05-18 22:35       ` pmarzo
2015-05-18 20:30         ` Joe Perches [this message]
2015-05-18 21:06     ` Dan Carpenter
2015-05-18 23:57       ` pmarzo
2015-05-18 16:23 ` Sudip Mukherjee
2015-05-18 21:50   ` pmarzo

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=1431981013.2870.82.camel@perches.com \
    --to=joe@perches.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dilekuzulmez@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haticeerturk27@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marzo.pedro@gmail.com \
    --cc=navyasri.tech@gmail.com \
    /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