All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Date: Wed, 27 Mar 2019 02:10:04 +0000	[thread overview]
Message-ID: <bug-198699-62941-xFJv8jG9Z1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198699-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Daniel van Vugt (daniel.van.vugt@canonical.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.van.vugt@canonical.c
                   |                            |om

--- Comment #26 from Daniel van Vugt (daniel.van.vugt@canonical.com) ---
Comment 24 suggests to me that this bug should be closed (?). Because it seems
to eliminate the possibility of the message appearing with (0x0f).

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

      parent reply	other threads:[~2019-03-27  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-198699-62941@https.bugzilla.kernel.org/>
2018-10-22 12:43 ` [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) bugzilla-daemon
2018-10-27  4:08 ` bugzilla-daemon
2018-10-27  4:13 ` bugzilla-daemon
2018-10-27  4:17 ` bugzilla-daemon
2018-10-30 19:15 ` bugzilla-daemon
2018-11-04 12:00 ` bugzilla-daemon
2018-11-12 14:22 ` bugzilla-daemon
2018-11-12 17:34 ` bugzilla-daemon
2019-01-18  6:31 ` bugzilla-daemon
2019-01-18  7:22 ` bugzilla-daemon
2019-02-01 21:28 ` bugzilla-daemon
2019-03-27  2:10 ` 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-198699-62941-xFJv8jG9Z1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.