From: Greg KH <gregkh@suse.de>
To: Joe Peterson <joe@skyrush.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] n_tty: honor opost flag for echoes
Date: Tue, 4 Aug 2009 14:25:38 -0700 [thread overview]
Message-ID: <20090804212538.GA26478@suse.de> (raw)
In-Reply-To: <4A789AA1.5070907@skyrush.com>
On Tue, Aug 04, 2009 at 02:31:29PM -0600, Joe Peterson wrote:
> Fixes the following bug:
>
> http://bugs.linuxbase.org/show_bug.cgi?id=2692
>
> Causes processing of echoed characters (output from the echo buffer) to
> honor the O_OPOST flag. This re-establishes this behavior.
>
> Note that this and the next patch ("n_tty: move echoctl check and
> clean up logic") were verified together by the bug reporters, and
> all tty tests now pass.
What "tty tests" would that be? Have a pointer to them?
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-04 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 20:31 [PATCH 1/2] n_tty: honor opost flag for echoes Joe Peterson
2009-08-04 21:25 ` Greg KH [this message]
2009-08-04 21:31 ` Joe Peterson
2009-08-04 23:52 ` Greg KH
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=20090804212538.GA26478@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=joe@skyrush.com \
--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