public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 00/14] Some BKL killing in the serial drivers
Date: Thu, 01 Apr 2010 17:04:08 +0100	[thread overview]
Message-ID: <20100401155513.8882.54006.stgit@localhost.localdomain> (raw)


---

Alan Cox (14):
      synclink: reworking locking a bit
      specialix; Kill the BKL
      epca: Kill the big kernel lock
      cyclades: Kill off BKL usage
      synclink: kill the big kernel lock
      rocket: kill BKL
      isicom: kill off the BKL
      riscom8: kill use of lock_kernel
      istallion: use bit ops for the board flags
      stallion: prune lock_kernel calls
      vc: Locking clean up
      tty: serial - fix various misuses/mishandlings of port->tty
      tty: serial - fix tty back references in termios
      tty: serial - fix tty referencing in set_ldisc


 drivers/char/cyclades.c      |   20 +++-----
 drivers/char/epca.c          |    4 --
 drivers/char/isicom.c        |   12 ++---
 drivers/char/istallion.c     |   59 ++++++++++++----------
 drivers/char/riscom8.c       |   14 +++--
 drivers/char/rocket.c        |   28 +++++++----
 drivers/char/selection.c     |    4 ++
 drivers/char/specialix.c     |   11 ++--
 drivers/char/stallion.c      |   20 +++++---
 drivers/char/synclink.c      |   19 ++++---
 drivers/char/synclink_gt.c   |   90 +++++++++++++++++-----------------
 drivers/char/synclinkmp.c    |   41 ++++++++--------
 drivers/char/vt.c            |    8 ++-
 drivers/serial/21285.c       |   10 +---
 drivers/serial/bfin_5xx.c    |    7 +--
 drivers/serial/imx.c         |   10 ++--
 drivers/serial/ioc3_serial.c |    9 ++-
 drivers/serial/ioc4_serial.c |    9 ++-
 drivers/serial/max3100.c     |    3 -
 drivers/serial/serial_core.c |  111 +++++++++++++++++++++++-------------------
 include/linux/serial_core.h  |    2 -
 21 files changed, 258 insertions(+), 233 deletions(-)

-- 


             reply	other threads:[~2010-04-01 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 16:04 Alan Cox [this message]
2010-04-01 16:04 ` [PATCH 01/14] tty: serial - fix tty referencing in set_ldisc Alan Cox
2010-04-01 16:04 ` [PATCH 02/14] tty: serial - fix tty back references in termios Alan Cox
2010-04-01 16:04 ` [PATCH 03/14] tty: serial - fix various misuses/mishandlings of port->tty Alan Cox
2010-04-01 16:04 ` [PATCH 04/14] vc: Locking clean up Alan Cox
2010-04-30 20:30   ` Arnd Bergmann
2010-04-01 16:05 ` [PATCH 05/14] stallion: prune lock_kernel calls Alan Cox
2010-04-29 21:29   ` Arnd Bergmann
2010-04-30 19:32     ` Alan Cox
2010-04-01 16:05 ` [PATCH 06/14] istallion: use bit ops for the board flags Alan Cox
2010-04-01 16:05 ` [PATCH 07/14] riscom8: kill use of lock_kernel Alan Cox
2010-04-01 16:05 ` [PATCH 08/14] isicom: kill off the BKL Alan Cox
2010-04-01 16:06 ` [PATCH 09/14] rocket: kill BKL Alan Cox
2010-04-01 16:06 ` [PATCH 10/14] synclink: kill the big kernel lock Alan Cox
2010-04-01 16:06 ` [PATCH 11/14] cyclades: Kill off BKL usage Alan Cox
2010-04-01 16:06 ` [PATCH 12/14] epca: Kill the big kernel lock Alan Cox
2010-04-01 16:07 ` [PATCH 13/14] specialix; Kill the BKL Alan Cox
2010-04-01 16:07 ` [PATCH 14/14] synclink: reworking locking a bit 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=20100401155513.8882.54006.stgit@localhost.localdomain \
    --to=alan@linux.intel.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