From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Alon Bar-Lev" <alon.barlev@gmail.com>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
linux-kernel@vger.kernel.org, bluez-devel@lists.sourceforge.net
Subject: Re: [BUG] rfcomm]
Date: Wed, 24 Oct 2007 00:10:35 +0200 [thread overview]
Message-ID: <200710240010.35799.rjw@sisk.pl> (raw)
In-Reply-To: <9e0cf0bf0710231057lf60ce17ldd38489850cdf7c5@mail.gmail.com>
On Tuesday, 23 October 2007 19:57, Alon Bar-Lev wrote:
> On 10/23/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> > first of all, please check if this still happens with 2.6.23, because we
> > had some patches in the area of the RFCOMM TTY code that might have
> > fixed this.
>
> These messages are of 2.6.23.
>
> > Second, can you try without uswsusp or suspend2. Both of
> > them are not upstream and I can't tell how much these would effect this
> > kind of behavior.
>
> How can I test this without doing suspend?
> uswsusp is not upstream?!?! Rafael?
It is upstream and is supposed to work.
Greetings,
Rafael
next prev parent reply other threads:[~2007-10-23 21:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 17:50 [BUG] rfcomm] Alon Bar-Lev
2007-10-23 17:55 ` Marcel Holtmann
2007-10-23 17:57 ` Alon Bar-Lev
2007-10-23 18:26 ` Marcel Holtmann
2007-10-23 18:28 ` Alon Bar-Lev
2007-10-23 22:10 ` Rafael J. Wysocki [this message]
2007-10-23 18:06 ` Jiri Kosina
2007-10-23 18:25 ` Marcel Holtmann
2007-10-23 18:27 ` Alon Bar-Lev
2007-10-23 18:30 ` Marcel Holtmann
2007-10-23 18:55 ` Alon Bar-Lev
2007-10-24 8:43 ` Cornelia Huck
2007-10-23 18:28 ` Jiri Kosina
2007-10-24 9:56 ` Pavel Machek
2007-11-05 5:08 ` [Bluez-devel] " Dave Young
2007-11-05 15:46 ` Alon Bar-Lev
2007-11-06 1:48 ` Dave Young
2007-11-06 2:49 ` Dave Young
2007-11-06 5:49 ` Alon Bar-Lev
2008-02-11 15:57 ` [BUG] rfcomm Alon Bar-Lev
2008-02-11 22:48 ` Frederik Deweerdt
2008-02-13 7:58 ` Andrew Morton
2008-02-13 16:58 ` Mark Lord
2008-02-15 3:28 ` Dave Young
2008-02-15 23:13 ` Dave Young
2008-02-16 21:49 ` Alon Bar-Lev
2008-02-20 10:36 ` Dave Young
2008-02-20 11:16 ` [Bluez-devel] " Stefan Seyfried
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=200710240010.35799.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alon.barlev@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).