Linux bluetooth development
 help / color / mirror / Atom feed
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 19:47:59 +0000	[thread overview]
Message-ID: <bug-198953-62941-U5BfYflpv7@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 #19 from Robert R. Howell (rhowell@uwyo.edu) ---
Hi Hans

Adding the "Reported-and-tested-by" tag would be fine.  

While I've been building kernels with a few special patches for my Baytrail
devices for the last couple years I'm just starting to learn how git is used
with the main repositories, and how to post patches and commits to the mailing
lists.  So I'm more than happy to have you add the Encore information in your
patch.

I don't yet have a public repository for the patches I use -- they are mostly
from the files at the Ubuntu ASUS T100 group at
<https://plus.google.com/communities/117853703024346186936>, with a few extra
of my own.  But I'm certainly happy to share those.  Let me think about the
best way to do that and I'll get back to you with a direct email on that.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2018-03-15 19:47 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
2018-03-15 19:47 ` bugzilla-daemon [this message]
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-U5BfYflpv7@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