From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
Paul Hardwick <p.hardwick@option.com>
Subject: Re: [PATCH] tty/serial: Lay the foundations for the next set of reworks
Date: Tue, 8 Apr 2008 23:13:48 +0100 [thread overview]
Message-ID: <20080408231348.190abf20@core> (raw)
In-Reply-To: <47FBEA09.6090507@gmail.com>
> Well, how exactly the card behaves on 1 byte write? And how did the .write
> protect against it?
One byte writes work fine via the write path and already occur. I suspect
the original author forgot to turn echo off and saw fun things happening
between the inbuilt modem emulation and the Linux side.
next prev parent reply other threads:[~2008-04-08 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 15:58 [PATCH] tty/serial: Lay the foundations for the next set of reworks Alan Cox
2008-04-08 21:56 ` Jiri Slaby
2008-04-08 22:13 ` Alan Cox [this message]
2008-04-09 6:57 ` Jiri Slaby
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=20080408231348.190abf20@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.hardwick@option.com \
/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