From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 199351] intel 8265 bluetooth no longer functions as of 4.16
Date: Fri, 13 Apr 2018 05:00:48 +0000 [thread overview]
Message-ID: <bug-199351-62941-T6vEhPD2xY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199351-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199351
--- Comment #8 from Bernd Steinhauser (linux@bernd-steinhauser.de) ---
Interesting, because that's exactly the option that I found to cause my problem
as well, even though the outcome seems to be different. ;)
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2018-04-13 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199351-62941@https.bugzilla.kernel.org/>
2018-04-13 3:29 ` [Bug 199351] intel 8265 bluetooth no longer functions as of 4.16 bugzilla-daemon
2018-04-13 5:00 ` bugzilla-daemon [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=bug-199351-62941-T6vEhPD2xY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@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).