linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 120691] UART HCI memory leak
Date: Tue, 23 Aug 2016 09:35:52 +0000	[thread overview]
Message-ID: <bug-120691-62941-xQaspQt0I3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-120691-62941@https.bugzilla.kernel.org/>

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

nico.edev@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |PATCH_ALREADY_AVAILABLE

--- Comment #17 from nico.edev@gmail.com ---
Exactly; I tried this patch and the leak disappeared:
http://marc.info/?l=linux-bluetooth&m=147193208628547

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

      parent reply	other threads:[~2016-08-23  9:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 13:46 [Bug 120691] New: UART HCI memory leak bugzilla-daemon
2016-06-22 10:00 ` [Bug 120691] " bugzilla-daemon
2016-06-22 16:38 ` bugzilla-daemon
2016-07-10  3:11 ` bugzilla-daemon
2016-07-10  3:12 ` bugzilla-daemon
2016-07-19 20:57 ` bugzilla-daemon
2016-07-20  8:06 ` bugzilla-daemon
2016-08-01 15:55 ` bugzilla-daemon
2016-08-01 17:35 ` bugzilla-daemon
2016-08-04 13:57 ` bugzilla-daemon
2016-08-04 14:52 ` bugzilla-daemon
2016-08-04 14:53 ` bugzilla-daemon
2016-08-07  0:58 ` bugzilla-daemon
2016-08-07  0:58 ` bugzilla-daemon
2016-08-17 21:30 ` bugzilla-daemon
2016-08-22 12:39 ` bugzilla-daemon
2016-08-22 14:18 ` bugzilla-daemon
2016-08-23  9:35 ` 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-120691-62941-xQaspQt0I3@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 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).