From: Greg KH <greg@kroah.com>
To: Vikram Dhillon <dhillonv10@gmail.com>
Cc: gregkh@suse.de, andrea.gelmini@gelma.net, linville@tuxdriver.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Staging: arlan: arlan.h: Fixed some style issues
Date: Wed, 28 Apr 2010 11:40:31 -0700 [thread overview]
Message-ID: <20100428184031.GC1748@kroah.com> (raw)
In-Reply-To: <1268613570-8975-1-git-send-email-dhillonv10@gmail.com>
On Sun, Mar 14, 2010 at 08:39:30PM -0400, Vikram Dhillon wrote:
> Fixed some style issues in accordance with checkpatch.pl. Before the
> patch contained "total: 2 errors, 186 warnings, 535 lines checked" and
> now it has: total: 0 errors, 170 warnings. Most of the warnings that
> remain now are the line over 80 chars ones.
Looks great, now queued up.
greg k-h
prev parent reply other threads:[~2010-04-28 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 0:39 [PATCH] Staging: arlan: arlan.h: Fixed some style issues Vikram Dhillon
2010-04-28 18:40 ` 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=20100428184031.GC1748@kroah.com \
--to=greg@kroah.com \
--cc=andrea.gelmini@gelma.net \
--cc=devel@driverdev.osuosl.org \
--cc=dhillonv10@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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