From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [bluetooth-next 00/16] l2cap.c split
Date: Fri, 4 Feb 2011 11:44:38 -0200 [thread overview]
Message-ID: <20110204134438.GA2151@joana> (raw)
In-Reply-To: <AANLkTi=P8dnzL9O-SatX_-zddHKndOLxA1vm3V1K+oji@mail.gmail.com>
Hi Luiz,
* Luiz Augusto von Dentz <luiz.dentz@gmail.com> [2011-02-04 14:38:13 +0200]:
> Hi,
>
> On Fri, Feb 4, 2011 at 8:01 AM, Gustavo F. Padovan
> <padovan@profusion.mobi> wrote:
> > Here is the first real split of l2cap.c file. That file was getting so big that
> > we really need to split it in two or more. By now we have two file:
> > l2cap_sock.c and l2cap_core.c. In l2cap_sock.c we have all functions that deals
> > with sockets, in l2cap_core.c the rest.
> >
> > Side efects are that I had to move the declaration of many functions to l2cap.h
> > along the l2cap socket list.
> >
> > There are more steps on this, but this is surely a big one.
>
> What about creating a l2cap directory like rfcomm? Or that would cause
> too much hassle with building system?
We plan to merge l2cap.ko and sco.ko modules into bluetooth.ko. That is the
reason why I'm doing it the net/bluetooth/ directory. There isn't a good use
case where one won't want to use the l2cap.ko and sco.ko modules and it will
be always possible to disable L2CAP and SCO in the menuconfig.
Regards,
--
Gustavo F. Padovan
http://profusion.mobi
prev parent reply other threads:[~2011-02-04 13:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 6:01 [bluetooth-next 00/16] l2cap.c split Gustavo F. Padovan
[not found] ` <1296799318-5517-2-git-send-email-padovan@profusion.mobi>
2011-02-04 6:01 ` [bluetooth-next 02/16] Bluetooth: Initial work for L2CAP split Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 03/16] Bluetooth: move l2cap_sock_ops to l2cap_sock.c Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 04/16] Bluetooth: move l2cap_sock_release() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 05/16] Bluetooth: move l2cap_sock_bind()/listen() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 06/16] Bluetooth: move l2cap_sock_accept() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 07/16] Bluetooth: move l2cap_sock_getname() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 08/16] Bluetooth: move l2cap_sock_setsockopt() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 09/16] Bluetooth: move l2cap_sock_getsockopt() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 10/16] Bluetooth: move l2cap_sock_connect() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 11/16] Bluetooth: move l2cap_sock_recvmsg() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 12/16] Bluetooth: move l2cap_sock_shutdown() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 13/16] Bluetooth: move l2cap_sock_sendmsg() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 14/16] Bluetooth: move L2CAP sock timers function " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 15/16] Bluetooth: move l2cap_sock_kill() " Gustavo F. Padovan
2011-02-04 6:01 ` [bluetooth-next 16/16] Bluetooth: move __l2cap_sock_close() " Gustavo F. Padovan
2011-02-04 12:38 ` [bluetooth-next 00/16] l2cap.c split Luiz Augusto von Dentz
2011-02-04 13:44 ` Gustavo F. 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=20110204134438.GA2151@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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).