From: "Valerio Vanni" <valerio@valeriovanni.com>
To: linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] serial: core: Preserve termios c_cflag for console resume
Date: Thu, 5 Jun 2014 01:31:43 +0200 [thread overview]
Message-ID: <lmoa97$q3h$1@ger.gmane.org> (raw)
In-Reply-To: 538F3150.6040102@hurleysoftware.com
"Peter Hurley" <peter@hurleysoftware.com> ha scritto nel messaggio
news:538F3150.6040102@hurleysoftware.com
> On 06/04/2014 10:22 AM, Greg Kroah-Hartman wrote:
>> Same as before, regression, or just a normal "new feature"?
>
> This was reported as a regression since 2.6.24, but that was likely
> misreported, and more likely due to a userspace update which triggers
> the bug.
>
> I would be surprised if console resume _never_ worked if the serial
> tty was opened then closed, but it probably has worked for a long
> time.
I don't know what was my initial mistake, but I realized very soon it was
not a regression and took away the "regression" flag from bugzilla.
I tried many and many kernels and all were failing. I tried also to go
down from 2.6.24 version, but I had to stop rather early because at some
point the kernels were incompatible with distribution (I don't remember
the details since I did these tests some month ago, and later I tested
only newer kernel versions).
The patches you sent are for -next? for -rc? for stable?
Can I try them on 3.13.11? (at the moment I'm using this)
WARNING: multiple messages have this Message-ID (diff)
From: "Valerio Vanni" <valerio@valeriovanni.com>
To: linux-kernel@vger.kernel.org
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/2] serial: core: Preserve termios c_cflag for console resume
Date: Thu, 5 Jun 2014 01:31:43 +0200 [thread overview]
Message-ID: <lmoa97$q3h$1@ger.gmane.org> (raw)
In-Reply-To: 538F3150.6040102@hurleysoftware.com
"Peter Hurley" <peter@hurleysoftware.com> ha scritto nel messaggio
news:538F3150.6040102@hurleysoftware.com
> On 06/04/2014 10:22 AM, Greg Kroah-Hartman wrote:
>> Same as before, regression, or just a normal "new feature"?
>
> This was reported as a regression since 2.6.24, but that was likely
> misreported, and more likely due to a userspace update which triggers
> the bug.
>
> I would be surprised if console resume _never_ worked if the serial
> tty was opened then closed, but it probably has worked for a long
> time.
I don't know what was my initial mistake, but I realized very soon it was
not a regression and took away the "regression" flag from bugzilla.
I tried many and many kernels and all were failing. I tried also to go
down from 2.6.24 version, but I had to stop rather early because at some
point the kernels were incompatible with distribution (I don't remember
the details since I did these tests some month ago, and later I tested
only newer kernel versions).
The patches you sent are for -next? for -rc? for stable?
Can I try them on 3.13.11? (at the moment I'm using this)
next prev parent reply other threads:[~2014-06-04 23:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:53 serial console does not wake from S3 suspend Valerio Vanni
2014-05-30 9:53 ` Valerio Vanni
2014-06-04 14:16 ` [PATCH 1/2] serial: core: Don't drop DTR if system console Peter Hurley
2014-06-04 14:16 ` [PATCH 2/2] serial: core: Preserve termios c_cflag for console resume Peter Hurley
2014-06-04 14:22 ` Greg Kroah-Hartman
2014-06-04 14:46 ` Peter Hurley
2014-06-04 14:48 ` Peter Hurley
2014-06-04 23:31 ` Valerio Vanni [this message]
2014-06-04 23:31 ` Valerio Vanni
2014-06-05 8:58 ` Valerio Vanni
2014-06-04 14:22 ` [PATCH 1/2] serial: core: Don't drop DTR if system console Greg Kroah-Hartman
2014-06-04 14:36 ` Peter Hurley
2014-06-09 13:08 ` One Thousand Gnomes
2014-06-10 1:20 ` Peter Hurley
2014-06-10 11:01 ` One Thousand Gnomes
2014-06-10 12:30 ` 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='lmoa97$q3h$1@ger.gmane.org' \
--to=valerio@valeriovanni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.