From: Greg KH <greg@kroah.com>
To: Gustavo Silva <silvagustavosilva@gmail.com>
Cc: gregkh@suse.de, alan@linux.intel.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Gustavo Silva <silvagustavo@users.sourceforge.net>
Subject: Re: [PATCH] Staging: memrar: fix coding style issues in memrar_handler.c
Date: Wed, 23 Jun 2010 15:18:49 -0700 [thread overview]
Message-ID: <20100623221849.GA15093@kroah.com> (raw)
In-Reply-To: <1277264253-10583-1-git-send-email-silvagustavo@users.sourceforge.net>
On Tue, Jun 22, 2010 at 10:37:33PM -0500, Gustavo Silva wrote:
> This is a patch to the memrar_handler.c file that fixes up the following
> issues:
>
> ERROR: trailing whitespace
> ERROR: code indent should use tabs where possible
> WARNING: please, no space before tabs
Sorry, someone just sent this one in and I applied it yesterday :(
Care to find some other code in here to clean up?
greg k-h
prev parent reply other threads:[~2010-06-23 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 3:37 [PATCH] Staging: memrar: fix coding style issues in memrar_handler.c Gustavo Silva
2010-06-23 22:18 ` Greg KH [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=20100623221849.GA15093@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=silvagustavo@users.sourceforge.net \
--cc=silvagustavosilva@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