From: Johan Hedberg <johan.hedberg@gmail.com>
To: Norbert Holze <norbert.holze@web.de>
Cc: linux-bluetooth@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: btusb regression / 0a12:0001 CSR
Date: Thu, 27 Aug 2015 13:27:11 +0300 [thread overview]
Message-ID: <20150827102711.GA28958@t440s.lan> (raw)
In-Reply-To: <55DB58B7.5080101@web.de>
Hi Norbert,
On Mon, Aug 24, 2015, Norbert Holze wrote:
> Is it possible to add a quirk or something else?
This was reported in the kernel.org bug tracker as well. Could you try
the patch proposal that I've attached there:
https://bugzilla.kernel.org/show_bug.cgi?id=103451
In the bug report it's just a single patch but I'll probably split it
into two for the final upstream submission.
Johan
prev parent reply other threads:[~2015-08-27 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 6:51 btusb regression / 0a12:0001 CSR Norbert Holze
2015-08-09 17:44 ` Marcel Holtmann
2015-08-09 17:57 ` Norbert Holze
2015-08-24 17:46 ` Aw: " Norbert Holze
2015-08-24 17:47 ` Norbert Holze
2015-08-27 10:27 ` Johan Hedberg [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=20150827102711.GA28958@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=norbert.holze@web.de \
/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).