public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Micki Balanga <micki@n-trig.com>
Cc: Jiri Kosina <jkosina@suse.cz>, "gregkh@suse.de" <gregkh@suse.de>,
	"jim.collar@eqware.net" <jim.collar@eqware.net>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: misc: Add N-trig firmware driver
Date: Tue, 5 Oct 2010 05:46:37 -0700	[thread overview]
Message-ID: <20101005124637.GB2943@kroah.com> (raw)
In-Reply-To: <6EF693376E00E2458E26FEC229232B128AAE23@Exchange2010-IL.n-trig.com>

On Tue, Oct 05, 2010 at 06:59:43AM +0000, Micki Balanga wrote:
> 
> 
> > -----Original Message-----
> > From: Jiri Kosina [mailto:jkosina@suse.cz]
> > Sent: Monday, October 04, 2010 2:58 PM
> > To: Greg KH
> > Cc: Micki Balanga; gregkh@suse.de; jim.collar@eqware.net; linux-
> > usb@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] USB: misc: Add N-trig firmware driver
> > 
> > On Sun, 3 Oct 2010, Greg KH wrote:
> > 
> > > >
> > >
> > > Can you please attach this in a non-base64 format so it can be
> > properly
> > > reviewed, and then, applied if applicable?
> > >
> > > Note, please run the patch through the scripts/checkpatch.pl tool
> > first
> > > before sending it out, so we don't just say the same things it finds
> > :)
> > 
> > As we already have HID driver for n-trig, could this whole thing
> > perhaps
> > be made part of it?
> > 
> > --
> > Jiri Kosina
> > SUSE Labs, Novell Inc.
> 
> The driver communicates with the bulk in/out endpoint. 

Why does it have to be a driver at all?  Why can't you just use libusb
or usbfs to implement this?

> It was written as a standalone module, because it does not use any HID
> subsystem services, and to ensure that the HID driver would not be too
> complex. 
> 
> The driver has been tested over several weeks at our company.
> The  patch was prepared and checked using the Checkpatch utility.

You might want to check that last step, it didn't seem to work properly
as the patch you sent could not be applied, due to it being base64
encoded :)

thanks,

greg k-h

  reply	other threads:[~2010-10-05 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03  7:56 [PATCH] USB: misc: Add N-trig firmware driver Micki Balanga
2010-10-04  1:19 ` Greg KH
2010-10-04 12:58   ` Jiri Kosina
2010-10-05  6:59     ` Micki Balanga
2010-10-05 12:46       ` Greg KH [this message]
2010-10-06  4:47         ` Micki Balanga
2010-10-06 14:04           ` 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=20101005124637.GB2943@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=jim.collar@eqware.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=micki@n-trig.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