From: Szymon Janc <szymon.janc@codecoup.pl>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] autopair: Add more common PIN codes for audio devices
Date: Tue, 26 Mar 2019 11:53:25 +0100 [thread overview]
Message-ID: <1577665.qXM628sudz@ix> (raw)
In-Reply-To: <66544e21401986edd519e4f6939e405eea5c7397.camel@hadess.net>
Hi Bastien,
On Monday, 25 March 2019 12:10:52 CET Bastien Nocera wrote:
> On Mon, 2017-11-27 at 16:28 +0100, Bastien Nocera wrote:
> > On Mon, 2017-11-27 at 16:26 +0100, Bastien Nocera wrote:
> > > PIN codes "1111", and "1234" are fairly common PIN codes used for
> > > audio
> > > devices such as speakers and headsets. This replaces similar quirks
> > > already present in gnome-bluetooth's PIN database.
> >
> > V2 of this patch, I've tested it again, and it seems to work in my
> > tests. I've also added another special case for gaming input devices
> > and remote controls in a second patch.
>
> The 2 patches in this patchset still apply, and are still relevant.
> Could those be reviewed and merged, please?
>
> Cheers
I've must have miss those, sorry for that.
Both patches are now applied.
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2019-03-26 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 15:26 [PATCH v2 1/2] autopair: Add more common PIN codes for audio devices Bastien Nocera
2017-11-27 15:26 ` [PATCH v2 2/2] autopair: Add pin codes to try for gaming input devices Bastien Nocera
2017-11-27 15:28 ` [PATCH v2 1/2] autopair: Add more common PIN codes for audio devices Bastien Nocera
2019-03-25 11:10 ` Bastien Nocera
2019-03-26 10:53 ` Szymon Janc [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=1577665.qXM628sudz@ix \
--to=szymon.janc@codecoup.pl \
--cc=hadess@hadess.net \
--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).