From: Gustavo Padovan <padovan@profusion.mobi>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 4/4] Bluetooth: hidp: Don't release device ref if never held
Date: Thu, 11 Aug 2011 18:07:16 -0300 [thread overview]
Message-ID: <20110811210716.GE19699@joana> (raw)
In-Reply-To: <1312555921.2172.14.camel@THOR>
Hi Peter,
* Peter Hurley <peter@hurleysoftware.com> [2011-08-05 10:52:01 -0400]:
> When an hidp connection is added for a boot protocol input
> device, don't release a device reference that was never
> acquired. The device reference is acquired when the session
> is linked to the session list (which hasn't happened yet when
> hidp_setup_input is called).
>
> Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
> ---
> net/bluetooth/hidp/core.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
All four patches applied. Thanks.
Gustavo
prev parent reply other threads:[~2011-08-11 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 14:52 [PATCH 4/4] Bluetooth: hidp: Don't release device ref if never held Peter Hurley
2011-08-11 21:07 ` Gustavo Padovan [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=20110811210716.GE19699@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/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).