From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2] Bluetooth: AMP: Get amp_mgr reference in HS hci_conn
Date: Thu, 18 Oct 2012 07:28:17 -0300 [thread overview]
Message-ID: <20121018102817.GA19695@joana> (raw)
In-Reply-To: <1350555379-7462-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-10-18 13:16:19 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> When assigning amp_mgr in hci_conn (type AMP_LINK) get also reference.
> In hci_conn_del those references would be put for both conn types
> AMP_LINK and ACL_LINK associated with amp_mgr.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> include/net/bluetooth/a2mp.h | 2 +-
> net/bluetooth/a2mp.c | 4 +++-
> net/bluetooth/amp.c | 2 +-
> 3 files changed, 5 insertions(+), 3 deletions(-)
Patch has been applied to bluetooth-next. Thanks.
Gustavo
next prev parent reply other threads:[~2012-10-18 10:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 14:09 [RFCv1 1/7] Bluetooth: AMP: Use Loglink handle in ACL Handle field Andrei Emeltchenko
2012-10-12 14:10 ` [RFCv1 2/7] Bluetooth: AMP: Handle complete frames in l2cap Andrei Emeltchenko
2012-10-12 23:50 ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 3/7] Bluetooth: AMP: Drop packets when no l2cap conn exist Andrei Emeltchenko
2012-10-12 23:50 ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 4/7] Bluetooth: Send EFS Conf Rsp only for BR/EDR chan Andrei Emeltchenko
2012-10-12 23:51 ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 5/7] Bluetooth: AMP: Get amp_mgr reference in HS hci_conn Andrei Emeltchenko
2012-10-12 23:53 ` Marcel Holtmann
2012-10-15 8:31 ` Andrei Emeltchenko
2012-10-12 14:10 ` [RFCv1 6/7] Bluetooth: AMP: Zero amp_mgr pointer if removed Andrei Emeltchenko
2012-10-12 23:54 ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 7/7] Bluetooth: Zero bredr pointer when chan is deleted Andrei Emeltchenko
2012-10-12 23:54 ` Marcel Holtmann
2012-10-12 23:49 ` [RFCv1 1/7] Bluetooth: AMP: Use Loglink handle in ACL Handle field Marcel Holtmann
2012-10-15 8:58 ` [PATCHv2 0/6] AMP link fixes Andrei Emeltchenko
2012-10-15 8:58 ` [PATCHv2 1/6] Bluetooth: AMP: Use Loglink handle in ACL Handle field Andrei Emeltchenko
2012-10-15 8:58 ` [PATCHv2 2/6] Bluetooth: AMP: Handle complete frames in l2cap Andrei Emeltchenko
2012-10-15 8:58 ` [PATCHv2 3/6] Bluetooth: AMP: Drop packets when no l2cap conn exist Andrei Emeltchenko
2012-10-15 8:58 ` [PATCHv2 4/6] Bluetooth: Send EFS Conf Rsp only for BR/EDR chan Andrei Emeltchenko
2012-10-15 8:58 ` [PATCHv2 5/6] Bluetooth: AMP: Get amp_mgr reference in HS hci_conn Andrei Emeltchenko
2012-10-15 12:49 ` Gustavo Padovan
2012-10-15 13:21 ` Andrei Emeltchenko
2012-10-15 15:27 ` Gustavo Padovan
2012-10-18 10:16 ` [PATCHv2] " Andrei Emeltchenko
2012-10-18 10:28 ` Gustavo Padovan [this message]
2012-10-15 8:58 ` [PATCHv2 6/6] Bluetooth: Zero bredr pointer when chan is deleted Andrei Emeltchenko
2012-10-15 12:50 ` Gustavo Padovan
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=20121018102817.GA19695@joana \
--to=gustavo@padovan.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--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).