From: Gustavo Padovan <padovan@profusion.mobi>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] Bluetooth: Remove duplicated code in l2cap conn req
Date: Fri, 24 Feb 2012 18:21:54 -0200 [thread overview]
Message-ID: <20120224202154.GB28740@joana> (raw)
In-Reply-To: <1330092000-9420-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-02-24 16:00:00 +0200]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> The same sequence sending L2CAP Connection Request was
> used in several places. Using subroutine makes those
> places easy to read.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 49 +++++++++++++++++--------------------------
> 1 files changed, 19 insertions(+), 30 deletions(-)
Acked-by: Gustavo F. Padovan <padovan@profusion.mobi>
Gustavo
next prev parent reply other threads:[~2012-02-24 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 14:00 [RFC] Bluetooth: Remove duplicated code in l2cap conn req Andrei Emeltchenko
2012-02-24 16:36 ` Ulisses Furquim
2012-02-24 20:21 ` Gustavo Padovan [this message]
2012-02-24 20:29 ` Johan Hedberg
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=20120224202154.GB28740@joana \
--to=padovan@profusion.mobi \
--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