[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWtj0iDW+wEWdZPUfKGpLRkdvuTmYz3mw4hVGyvdy_HBw@mail.gmail.com>
Date: Sat, 19 Jan 2013 14:35:08 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>, Ilya Zykov <ilya@...x.ru>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux PM List <linux-pm@...ts.linux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: linux-next: Tree for Jan 18 [ BROKEN tty-next on suspend ]
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130117:
>
> Undropped tree: samung
>
> The powerpc tree still had a build failure.
>
> The driver-core tree gained a build failure for which I applied a merge
> fix patch.
>
> The gpio-lw tree gained a build failure so I used the version from
> next-20130117.
>
> The samsung tree lost the majority of its conflicts but gained more
> against the arm-soc and slave-dma tree.
>
> ----------------------------------------------------------------------------
>
[ TO TTY folks ] + [ CC Rafael and linux-pm ML ]
In the end it turned out to be a problem with tty-next (see thread in [1]).
I am hitting the problem reproducibly on PM/suspend.
Rafael gave me some cool help on pm-testing, thanks (see also thread in [1])
Ilya has sent a patch to [3] which needs to be refreshed.
AFAICS also be adapted to the recent changes to tty_port and tty_buf.
But hey, I am no TTY expert so it is up to you.
Hope you will CC me on the patch.
Thanks!
- Sedat -
[1] http://marc.info/?t=135854714000003&r=1&w=2
[2] http://git.kernel.org/?p=linux/kernel/git/gregkh/tty.git;a=shortlog;h=refs/heads/tty-next
[3] http://marc.info/?t=135452868300003&r=1&w=2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists