public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Robert Love <rml@tech9.net>, Alex Khripin <akhripin@mit.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: BKL in tty code?
Date: Wed, 30 Jan 2002 23:05:32 +0000	[thread overview]
Message-ID: <20020130230532.I19292@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020130210127.H19292@flint.arm.linux.org.uk> <Pine.LNX.4.10.10201301457450.7609-100000@www.transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10201301457450.7609-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Wed, Jan 30, 2002 at 02:58:29PM -0800

On Wed, Jan 30, 2002 at 02:58:29PM -0800, James Simmons wrote:
> All the locking should be moved to the upper tty layers. Why implement the
> wheel over and over agin for each type of tty device.

By that statement, I can see that you haven't really done any analysis of
the tty nor serial locking.  Its not a simple case of "just add a per tty
semaphore in the tty layer and everything will be fine".

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-01-30 23:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 18:49 BKL in tty code? Alex Khripin
2002-01-30 19:25 ` Robert Love
2002-01-30 21:01   ` Russell King
2002-01-30 22:58     ` James Simmons
2002-01-30 23:05       ` Russell King [this message]
2002-01-30 22:52         ` Karl
2002-01-30 23:14         ` James Simmons
2002-01-30 21:10   ` David C. Hansen
2002-01-30 21:57   ` Karl
2002-01-30 23:00     ` James Simmons
2002-01-30 22:57   ` James Simmons

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=20020130230532.I19292@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=akhripin@mit.edu \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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