From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Heads Up: tty locking changes
Date: Tue, 29 Jan 2008 14:09:36 +0000 [thread overview]
Message-ID: <20080129140936.0350d685@core> (raw)
In the next few days I'll be submitting some further tty locking changes
to the kernel. Line discipline ->write and ->read methods will no longer
be covered by lock_kernel. For the moment tty->driver write methods won't
change (that is they will be either lock_kernel or in an IRQ but never
both). That is next on the hit list once the lock is driven out of the
tty ldisc layer.
If you have any out of tree ldiscs please be ready. If you maintain any
serial drivers still relying on lock_kernel for internal locking on the
read/write paths, now would be a good time to fix them before they break
Alan
reply other threads:[~2008-01-29 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080129140936.0350d685@core \
--to=alan@lxorguk.ukuu.org.uk \
--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