linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tore Anderson <tore@fud.no>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389
Date: Thu, 3 Mar 2016 21:44:19 +0100	[thread overview]
Message-ID: <20160303214419.6ac7558a@envy.w5.y.home> (raw)
In-Reply-To: <20160303084229.GA15622@t440s.ger.corp.intel.com>

* Johan Hedberg

> One thing you could still try is use an even newer kernel, such as the
> bluetooth-next tree or the latest 4.5-rc release, and see if the issue
> still persists.

I did with fresh git pulls:

bluetooth-next @ 9dbadc0: Works
linux (torvalds) @ f983cd3: Broken

If you'd like I can try to bisect it this weekend to figure out exactly
where it got fixed, if not I'll just content myself with the knowledge
that it'll probably get fixed in the mainline kernel eventually.

Tore

  reply	other threads:[~2016-03-03 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 17:12 PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389 Tore Anderson
2016-02-20 18:23 ` Johan Hedberg
2016-02-20 18:29   ` Johan Hedberg
2016-02-20 20:30     ` Tore Anderson
2016-02-21  7:02       ` Johan Hedberg
2016-02-21 11:13         ` Tore Anderson
2016-03-03  7:51           ` Tore Anderson
2016-03-03  8:42             ` Johan Hedberg
2016-03-03 20:44               ` Tore Anderson [this message]
2016-03-04  6:54                 ` Johan Hedberg
2016-03-05  9:09                   ` Tore Anderson

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=20160303214419.6ac7558a@envy.w5.y.home \
    --to=tore@fud.no \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@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).