From: Jiri Slaby <jirislaby@gmail.com>
To: kagen101@gmail.com
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Simon Horman <horms@verge.net.au>,
devel <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Staging: dt3155: fix coding style issues in dt3155_drv.c
Date: Tue, 06 Jul 2010 10:58:58 +0200 [thread overview]
Message-ID: <4C32F052.6060202@gmail.com> (raw)
In-Reply-To: <1278367345.5396.64.camel@dermezel>
On 07/06/2010 12:02 AM, Joe Eloff wrote:
> --- a/drivers/staging/dt3155/dt3155_drv.c
> +++ b/drivers/staging/dt3155/dt3155_drv.c
> @@ -78,7 +78,7 @@ extern void printques(int);
> MODULE_LICENSE("GPL");
>
> /* Error variable. Zero means no error. */
> -int dt3155_errno = 0;
> +int dt3155_errno ;
Isn't this a checkpatch error :)?
--
js
next prev parent reply other threads:[~2010-07-06 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 22:02 [PATCH 2/2] Staging: dt3155: fix coding style issues in dt3155_drv.c Joe Eloff
2010-07-06 1:43 ` Simon Horman
2010-07-06 8:58 ` Jiri Slaby [this message]
2010-07-08 19:59 ` 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=4C32F052.6060202@gmail.com \
--to=jirislaby@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=horms@verge.net.au \
--cc=hsweeten@visionengravers.com \
--cc=kagen101@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox