From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ulrich Hahn <uhahn@eanco.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ..another device for the ftdi_sio driver, 2nd infusion
Date: Sun, 2 Feb 2014 10:32:52 +0100 [thread overview]
Message-ID: <20140202093252.GA9994@kroah.com> (raw)
In-Reply-To: <1391332936.30603.1@biblenovo>
On Sun, Feb 02, 2014 at 10:22:16AM +0100, Ulrich Hahn wrote:
> Thanks, Greg to your bot for the hint,
>
> gmail seems to screw up tabs for spaces. Good to know, learning by doing..
> Lets give it another try:
>
> >finally I prepared a patch for the famous ftdi_sio usb serial driver.
> >Adding two Tagsys RFID readers I am using.
> >After having asked Bill Ryder he suggested adressing the
> >linux-usb-devel mailing list. (what?)
>
> >Sorry for the mess below - I am not doing this frequently - being
> >rather a leecher over the last 20 years:-)
>
>
> Signed-off-by: Ulrich Hahn <uhahn@eanco.de>
That's better, but I have to edit the above by hand, which isn't a big
deal, but when you deal with tens of thousands of patches a year,
doesn't scale :(
>
> diff -uprN linux-source-3.2.0/drivers/usb/serial/ftdi_sio.c linux-source-3.2.0+tagsysRFID/drivers/usb/serial/ftdi_sio.c
> --- linux-source-3.2.0/drivers/usb/serial/ftdi_sio.c 2013-12-03 18:40:26.000000000 +0100
> +++ linux-source-3.2.0+tagsysRFID/drivers/usb/serial/ftdi_sio.c 2014-02-01 16:32:40.146698791 +0100
3.2.0 is over 2 years old, things have moved on a bit since then :)
Can you redo this patch against the 3.13.0 kernel release, to have a
chance for it to be able to be applied?
thanks,
greg k-h
prev parent reply other threads:[~2014-02-02 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 9:22 ..another device for the ftdi_sio driver, 2nd infusion Ulrich Hahn
2014-02-02 9:32 ` Greg Kroah-Hartman [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=20140202093252.GA9994@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=uhahn@eanco.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.