From: Oliver Neukum <oneukum@suse.de>
To: Jesse Sung <jesse.sung@canonical.com>
Cc: linux-bluetooth@vger.kernel.org, 812132@bugs.launchpad.net
Subject: Re: [PATCH] Bluetooth: set reset_resume handler
Date: Tue, 25 Oct 2011 20:29:55 +0200 [thread overview]
Message-ID: <201110252029.55900.oneukum@suse.de> (raw)
In-Reply-To: <4EA6CC5B.2020400@canonical.com>
Am Dienstag, 25. Oktober 2011, 16:48:59 schrieb Jesse Sung:
> Just tested file transferring. If there's no active connection,
> everything goes fine. But if a file is transferring while going to S3,
> bluetooth is not working after resume. Use applet to disable and
> re-enable bluetooth makes it work again...
>
> Wondering what is the right way to handle loss of power...
A virtual unplug/plug worked until now, even if it was inelegant.
Regards
Oliver
prev parent reply other threads:[~2011-10-25 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 8:37 [PATCH] Bluetooth: set reset_resume handler Jesse Sung
2011-10-25 8:40 ` Oliver Neukum
2011-10-25 11:20 ` Jesse Sung
2011-10-25 11:43 ` Oliver Neukum
2011-10-25 14:48 ` Jesse Sung
2011-10-25 18:29 ` Oliver Neukum [this message]
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=201110252029.55900.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=812132@bugs.launchpad.net \
--cc=jesse.sung@canonical.com \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).