From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 198953] hci_bcm: Streamline runtime PM code change for 4.16 kernel breaks bluetooth on ASUS T100TA
Date: Thu, 15 Mar 2018 18:31:48 +0000 [thread overview]
Message-ID: <bug-198953-62941-BLlnaEgQAB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198953-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198953
--- Comment #18 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
p.s.
Do you have a git repo or some such with the other Bay Trail patches you use
somewhere? As part of my ongoing Bay and Cherry Trail support work I'm trying
to get all patches from various places, such as:
https://github.com/burzumishi/linux-baytrail-flexx10/tree/master/kernel/patches/v4.8
https://github.com/muhviehstah/linux-baytrail411/commits/master
https://github.com/jfwells/linux-asus-t100ta
Upstream, so I'm always interested in what patches people use / need. Perhaps
there is even a patch in there which would be a good candidate for your first
upstream patch submission (you seem to know your way around the kernel, so I
believe you would make a good kernel dev).
Anyways this is offtopic for this bug, so please drop me a mail at
hdegoede@redhat.com about the the other Bay Trail patches you use (or file a
new bug for them).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-03-15 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198953-62941@https.bugzilla.kernel.org/>
2018-03-15 7:58 ` [Bug 198953] hci_bcm: Streamline runtime PM code change for 4.16 kernel breaks bluetooth on ASUS T100TA bugzilla-daemon
2018-03-15 8:03 ` bugzilla-daemon
2018-03-15 8:07 ` bugzilla-daemon
2018-03-15 8:08 ` bugzilla-daemon
2018-03-15 8:09 ` bugzilla-daemon
2018-03-15 17:06 ` bugzilla-daemon
2018-03-15 17:08 ` bugzilla-daemon
2018-03-15 17:09 ` bugzilla-daemon
2018-03-15 17:10 ` bugzilla-daemon
2018-03-15 17:21 ` bugzilla-daemon
2018-03-15 17:23 ` bugzilla-daemon
2018-03-15 18:25 ` bugzilla-daemon
2018-03-15 18:26 ` bugzilla-daemon
2018-03-15 18:31 ` bugzilla-daemon [this message]
2018-03-15 19:47 ` bugzilla-daemon
2018-03-15 20:01 ` bugzilla-daemon
2018-03-16 10:36 ` bugzilla-daemon
2018-03-18 3:49 ` bugzilla-daemon
2018-03-18 3:51 ` bugzilla-daemon
2018-03-18 16:54 ` bugzilla-daemon
2018-03-18 18:43 ` bugzilla-daemon
2018-03-20 7:45 ` bugzilla-daemon
2018-03-22 16:31 ` bugzilla-daemon
2018-03-27 15:07 ` bugzilla-daemon
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-198953-62941-BLlnaEgQAB@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).