From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 3/4] Bluetooth: Remove unneeded local_amp_id initialization
Date: Fri, 16 Nov 2012 08:53:57 +0900 [thread overview]
Message-ID: <1353023637.1849.1.camel@aeonflux> (raw)
In-Reply-To: <1352996096-27374-3-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> local_amp_id is already set in l2cap_connect() which is called several
> lines above.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 1 -
> 1 file changed, 1 deletion(-)
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-11-15 23:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 16:14 [RFC 1/4] Bluetooth: Use __l2cap_no_conn_pending helper Andrei Emeltchenko
2012-11-15 16:14 ` [RFC 2/4] Bluetooth: Fix sending L2CAP Create Chan Req Andrei Emeltchenko
2012-11-15 23:56 ` Marcel Holtmann
2012-11-15 16:14 ` [RFC 3/4] Bluetooth: Remove unneeded local_amp_id initialization Andrei Emeltchenko
2012-11-15 23:53 ` Marcel Holtmann [this message]
2012-11-15 16:14 ` [RFC 4/4] Bluetooth: Set local_amp_id after getting Phylink Completed evt Andrei Emeltchenko
2012-11-15 23:54 ` Marcel Holtmann
2012-11-19 21:28 ` Gustavo Padovan
2012-11-20 15:16 ` [RFC 0/4] Bluetooth: AMP fixes Andrei Emeltchenko
2012-11-20 15:16 ` [RFC 1/4] Bluetooth: Fix sending L2CAP Create Chan Req Andrei Emeltchenko
2012-11-20 15:16 ` [RFC 2/4] Bluetooth: Set local_amp_id after getting Phylink Completed evt Andrei Emeltchenko
2012-11-20 15:16 ` [RFC 3/4] Bluetooth: Improve error message printing Andrei Emeltchenko
2012-11-20 15:16 ` [RFC 4/4] Bluetooth: AMP: Set no FCS for incoming L2CAP chan Andrei Emeltchenko
2012-11-20 17:56 ` Gustavo Padovan
2012-11-15 23:53 ` [RFC 1/4] Bluetooth: Use __l2cap_no_conn_pending helper Marcel Holtmann
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=1353023637.1849.1.camel@aeonflux \
--to=marcel@holtmann.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).