From: Joe Perches <joe@perches.com>
To: Craig Inches <craig.inches@xayto.net>
Cc: lidza.louina@gmail.com, markh@compro.net,
gregkh@linuxfoundation.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: drivers: dgnc
Date: Thu, 16 Jul 2015 08:30:53 -0700 [thread overview]
Message-ID: <1437060653.16262.25.camel@perches.com> (raw)
In-Reply-To: <1437088293-12128-1-git-send-email-craig.inches@xayto.net>
On Thu, 2015-07-16 at 23:11 +0000, Craig Inches wrote:
> Fixed up some checkpatch.pl style issues.
> Line greater than 80 Chars in multiple locations.
I think most all of these are not improvements.
Please use --strict when verifying your patches.
Please fix the time on your system.
next prev parent reply other threads:[~2015-07-16 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 23:11 [PATCH] Staging: drivers: dgnc Craig Inches
2015-07-16 15:30 ` Joe Perches [this message]
2015-07-17 0:20 ` Craig Inches
2015-07-16 17:52 ` Joe Perches
2015-07-17 0:57 ` Craig Inches
2015-07-16 15:49 ` Greg KH
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=1437060653.16262.25.camel@perches.com \
--to=joe@perches.com \
--cc=craig.inches@xayto.net \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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