From: Alan Cox <alan@redhat.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
rmk+serial@arm.linux.org.uk, alan@redhat.com
Subject: Re: Moxa multi serial driver doesn't pass received chars up
Date: Thu, 2 Jun 2005 18:58:05 -0400 [thread overview]
Message-ID: <20050602225805.GB9628@devserv.devel.redhat.com> (raw)
In-Reply-To: <200506021554.07316.vda@ilport.com.ua>
On Thu, Jun 02, 2005 at 03:54:07PM +0300, Denis Vlasenko wrote:
> I am cooking a patch which will use
> tty_insert_flip_char(tty, ch, flag);
Cool. Thats the right way for it to work
next prev parent reply other threads:[~2005-06-02 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 9:20 Moxa multi serial driver doesn't pass received chars up Denis Vlasenko
2005-06-02 12:54 ` Denis Vlasenko
2005-06-02 22:58 ` Alan Cox [this message]
2005-06-03 13:01 ` [PATCH] moxa: do not ignore input Denis Vlasenko
2006-06-20 17:17 ` Sergei Organov
2006-06-21 11:51 ` Alan Cox
2006-06-21 11:41 ` Sergei Organov
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=20050602225805.GB9628@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
--cc=vda@ilport.com.ua \
/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).