From: Alan Cox <alan@linux.intel.com>
To: greg@kroah.com, linux-serial@vger.kernel.org
Subject: [PATCH 0/4] serial: move towards tty_port
Date: Wed, 19 May 2010 13:13:47 +0100 [thread overview]
Message-ID: <20100519121234.18011.51870.stgit@localhost.localdomain> (raw)
We really want to be using tty_port here so that we can dump all the nasty
horrible complicated locking and POSIX tty behaviour into one place for all
users. This gets us to the point of the block_til_ready helper doing much of
the work.
---
Alan Cox (4):
serial: Use block_til_ready helper
serial: trim locking on the helpers
serial: add port helpers
serial: Change the wait for carrier locking
drivers/serial/serial_core.c | 131 +++++++++++++++---------------------------
1 files changed, 46 insertions(+), 85 deletions(-)
--
Zendemonium
next reply other threads:[~2010-05-19 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 12:13 Alan Cox [this message]
2010-05-19 12:13 ` [PATCH 1/4] serial: Change the wait for carrier locking Alan Cox
2010-05-19 12:14 ` [PATCH 2/4] serial: add port helpers Alan Cox
2010-05-19 12:14 ` [PATCH 3/4] serial: trim locking on the helpers Alan Cox
2010-05-19 12:14 ` [PATCH 4/4] serial: Use block_til_ready helper 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=20100519121234.18011.51870.stgit@localhost.localdomain \
--to=alan@linux.intel.com \
--cc=greg@kroah.com \
--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).