public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "David A. Ranch" <dranch@trinnet.net>
Cc: Greg KH <greg@kroah.com>, bryder@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] small FTDI USB serial driver update
Date: Mon, 26 Jul 2010 10:43:14 -0700	[thread overview]
Message-ID: <20100726174314.GC17741@suse.de> (raw)
In-Reply-To: <4C4C4BD8.7040008@trinnet.net>

On Sun, Jul 25, 2010 at 07:36:08AM -0700, David A. Ranch wrote:
> 
> Hello Greg,
> 
> Thanks for getting back to me!  I didn't know what you meant by
> "Sign-off" but I just researched it per
> http://lwn.net/Articles/139918 (please let me know if that post
> doesn't apply anymore).  This will be my first kernel patch.  Let's
> try again:

Close, but it's a bit off.  Try looking at the version in the kernel
tree that you are patching against (should be 2.6.34 or newer).

> 
> Reason for patch:
> -----------------
> This patch is for a US Interface, Inc. "Navigator" USB device.
> Specifically, it's a HAM Radio USB sound modem that also
> incorporates three pairs of unique FTDI serial ports.  The standard
> Linux FTDI serial driver will only recognize the first two serial
> ports of an unknown FDTI derived device and this patch adds in
> recognition to these specific new IDs.
> 
> 
> Diffs are against a vanilla 2.6.34

The Signed-off-by: line should go here.

> 
> 
> --- ftdi_sio_ids.h.orig 2010-07-25 07:17:44.000000000 -0700
> +++ ftdi_sio_ids.h      2010-07-25 07:20:46.000000000 -0700

 need a full path to the driver, something like:
 	a/drivers/usb/serial/ftdi_sio_ids.h.orig


> @@ -40,6 +40,13 @@
> 
>  #define FTDI_NXTCAM_PID                0xABB8 /* NXTCam for
> Mindstorms NXT */
> 
> +/* US Interface Navigator (http://www.usinterface.com/). */
> +/* Submitted by David Ranch */
> +#define FTDI_USINT_CAT_PID     0xB810  /* Navigator CAT and 2nd PTT
> lines */

The patch is line-wrapped and can't be applied.

> +#define FTDI_USINT_WKEY_PID    0xB811  /* Navigator WKEY and FSK lines */
> +#define FTDI_USINT_RS232_PID   0xB812  /* Navigator RS232 and
> CONFIG lines */
> +
> +
>  /* OOCDlink by Joern Kaipf <joernk@web.de>
>   * (http://www.joernonline.de/dw/doku.php?id=start&idx=projects:oocdlink)
> */
>  #define FTDI_OOCDLINK_PID      0xbaf8  /* Amontec JTAGkey */
> 
> 
> 
> --- ftdi_sio.c.orig     2010-07-25 07:21:10.000000000 -0700
> +++ ftdi_sio.c  2010-07-25 07:24:21.000000000 -0700
> @@ -162,6 +162,9 @@ static struct usb_device_id id_table_com
>         { USB_DEVICE(FTDI_VID, FTDI_SCS_DEVICE_5_PID) },
>         { USB_DEVICE(FTDI_VID, FTDI_SCS_DEVICE_6_PID) },

Your email client stripped off the tabs and converted them to spaces,
making the patch impossible to apply.

Care to redo it all and try again?

thanks,

greg k-h

      reply	other threads:[~2010-07-26 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C4B826E.8050009@trinnet.net>
     [not found] ` <20100725045859.GA7631@kroah.com>
2010-07-25 14:36   ` [PATCH] small FTDI USB serial driver update David A. Ranch
2010-07-26 17:43     ` 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=20100726174314.GC17741@suse.de \
    --to=gregkh@suse.de \
    --cc=bryder@sgi.com \
    --cc=dranch@trinnet.net \
    --cc=greg@kroah.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