public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Peterson <joe@skyrush.com>
To: Greg KH <gregkh@suse.de>
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, 04 Aug 2009 15:31:35 -0600	[thread overview]
Message-ID: <4A78A8B7.7050300@skyrush.com> (raw)
In-Reply-To: <20090804212538.GA26478@suse.de>

Greg KH wrote:
> 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?

It's the "Linux Standard Base" test suite:

	http://www.linuxfoundation.org/collaborate/workgroups/lsb

Here's a link to the specific code - got this from one of the reporters:

http://bzr.linux-foundation.org/lsb/devel/runtime-test?cmd=content;rev=cyeoh-20020312084903-a08971416c59e5d5;pathrevid=stewb%40linux-foundation.org-20090626205411-sfb23cc0tjj7jzgm;path=modules/vsx-pcts/tset/POSIX.os/devclass/c_lflag/c_lflag.c


						-Joe

  reply	other threads:[~2009-08-04 21:31 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
2009-08-04 21:31   ` Joe Peterson [this message]
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=4A78A8B7.7050300@skyrush.com \
    --to=joe@skyrush.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --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