From: Greg KH <greg@kroah.com>
To: Peta Blaha <blahapeta@gmail.com>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input/joystick: add driver fortius 1942
Date: Mon, 16 Mar 2009 19:25:31 -0700 [thread overview]
Message-ID: <20090317022531.GA504@kroah.com> (raw)
In-Reply-To: <739e73230903161921u426f2c65gddbc089d25ba5d50@mail.gmail.com>
On Tue, Mar 17, 2009 at 03:21:18AM +0100, Peta Blaha wrote:
> Driver for Fortius 1942 device.
>
> Signed-off-by: Petr Blaha <blahapeta@gmail.com>
> ---
>
> --- a/drivers/input/joystick/fortius_1942.c.orig 1970-01-01
> 01:00:00.000000000 +0100
Your patch is linewrapped :(
> +++ b/drivers/input/joystick/fortius_1942.c 2009-03-17 03:17:01.000000000 +0100
> @@ -0,0 +1,394 @@
> +/*
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
Are you sure about "any later version"?
> + unsigned long difference = 0;
> + /*time measure*/
> + struct timeval time, time_before;
> + /*guessed fastest speed a man can possibly ride-incitating full
> + throttle*/
> + unsigned int fastest_wheel_rotate = 1000;
> + /*actual state of path reached in one cycle*/
> + unsigned int ride = 0, old_ride = 0;
These should all be static.
Have you run your code through scripts/checkpatch.pl?
> +struct usb_tfor {
> + char name[128];
Tabs are eaten by your email client :(
Care to try again?
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-17 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 2:21 [PATCH] input/joystick: add driver fortius 1942 Peta Blaha
2009-03-17 2:25 ` Greg KH [this message]
2009-03-21 5:46 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2009-03-19 13:51 Peta Blaha
2009-03-19 13:39 ` Felipe Balbi
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=20090317022531.GA504@kroah.com \
--to=greg@kroah.com \
--cc=blahapeta@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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