From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: tty/serial eating \n regression in 3.13-rc1
Date: Thu, 28 Nov 2013 10:46:14 -0700 [thread overview]
Message-ID: <20131128174614.GB28055@obsidianresearch.com> (raw)
In-Reply-To: <1385652419-4732-1-git-send-email-peter@hurleysoftware.com>
On Thu, Nov 28, 2013 at 10:26:57AM -0500, Peter Hurley wrote:
> Please test out the attached patch and let me know if that solves
> the login whitespace problem.
Yes, it certainly does:
Tested-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
My bisection search showed this should go into 3.12 stable and 3.13..
> Also, please retest the 'cat enable' problem; I have doubts that this
> patch fixes that problem, though.
Correct, this case is still broken, I had guessed they were the same..
Hmm.. it behaves that way in 3.10 as well.. And the issue happens when
the line exceeds 80 cols, and things visually look sane if my x
terminal is 80 cols. So this is something different and probably
expected behavior.
Thanks!
Jason
next prev parent reply other threads:[~2013-11-28 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 21:53 tty/serial eating \n regression in 3.13-rc1 Jason Gunthorpe
2013-11-27 12:13 ` Peter Hurley
2013-11-27 18:13 ` Jason Gunthorpe
2013-11-28 15:26 ` >> On 11/26/2013 04:53 PM, Jason Gunthorpe wrote: Peter Hurley
2013-11-28 17:46 ` Jason Gunthorpe [this message]
2013-11-29 12:39 ` tty/serial eating \n regression in 3.13-rc1 Peter Hurley
2013-11-29 17:32 ` Greg Kroah-Hartman
2013-11-29 17:56 ` [PATCH] n_tty: Fix missing newline echo Peter Hurley
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=20131128174614.GB28055@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.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