From: Alan Cox <alan@linux.intel.com>
To: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
greg@kroah.com, drosenberg@vsecurity.com
Subject: [PATCH 0/3] Fix the TIOCGICOUNT problem for good
Date: Thu, 16 Sep 2010 18:21:06 +0100 [thread overview]
Message-ID: <20100916171747.25987.33573.stgit@localhost.localdomain> (raw)
Remembering to clear fields is something driver authors are simply never
going to remember to get right every new driver. Instead take the problem
away from them and give them a simple interface to do the job.
---
Alan Cox (3):
tty: icount changeover for other main devices
tty: Convert the USB drivers to the new icount interface
tty: Make tiocgicount a handler
arch/ia64/hp/sim/simserial.c | 12 -----
drivers/char/amiserial.c | 56 ++++++++++++++-----------
drivers/char/cyclades.c | 49 ++++++++++++----------
drivers/char/ip2/ip2main.c | 71 +++++++++++++++++++-------------
drivers/char/mxser.c | 62 ++++++++++++++++------------
drivers/char/nozomi.c | 37 ++++++++---------
drivers/char/pcmcia/synclink_cs.c | 60 ++++++++++++---------------
drivers/char/synclink.c | 73 +++++++++++++++------------------
drivers/char/synclink_gt.c | 55 +++++++++++++------------
drivers/char/synclinkmp.c | 61 +++++++++++++---------------
drivers/char/tty_io.c | 21 +++++++++
drivers/net/usb/hso.c | 35 +++++++---------
drivers/serial/68360serial.c | 51 +++++++++++------------
drivers/serial/serial_core.c | 35 +++++++---------
drivers/usb/serial/ark3116.c | 40 +++++++++---------
drivers/usb/serial/ftdi_sio.c | 1
drivers/usb/serial/io_edgeport.c | 49 ++++++++++++----------
drivers/usb/serial/io_tables.h | 4 ++
drivers/usb/serial/io_ti.c | 29 ++++++++++---
drivers/usb/serial/mos7720.c | 50 +++++++++++++----------
drivers/usb/serial/mos7840.c | 50 +++++++++++++----------
drivers/usb/serial/ssu100.c | 46 +++++++++++----------
drivers/usb/serial/ti_usb_3410_5052.c | 37 +++++++++++++----
drivers/usb/serial/usb-serial.c | 13 ++++++
include/linux/tty_driver.h | 9 ++++
include/linux/usb/serial.h | 2 +
net/bluetooth/rfcomm/tty.c | 4 --
27 files changed, 561 insertions(+), 451 deletions(-)
--
Rust greets time a grave to steam, in mire gloom to no more gleam
Does care die quiet and scarred, Berry red in Barry yard ?
Rusted steel at rest dust all, old sump oil lead is my pall
long rather to linger there, cold my fire once called me fair
Who knows now when I was new, speed in flow and on I flew
I turned eyes to run and see, in steam a dream adore me
next reply other threads:[~2010-09-16 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 17:21 Alan Cox [this message]
2010-09-16 17:21 ` [PATCH 1/3] tty: Make tiocgicount a handler Alan Cox
2010-09-16 17:21 ` [PATCH 2/3] tty: Convert the USB drivers to the new icount interface Alan Cox
2010-09-16 17:21 ` [PATCH 3/3] tty: icount changeover for other main devices Alan Cox
2010-09-16 18:44 ` [PATCH 0/3] Fix the TIOCGICOUNT problem for good Greg KH
2010-09-16 22:01 ` Alan Cox
2010-09-17 4:56 ` David Miller
2010-09-17 17:01 ` Greg KH
2010-09-18 15:58 ` Christoph Hellwig
2010-09-20 8:31 ` Alan Cox
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=20100916171747.25987.33573.stgit@localhost.localdomain \
--to=alan@linux.intel.com \
--cc=drosenberg@vsecurity.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).