From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org,
"Gustavo F. Padovan" <padovan@profusion.mobi>
Subject: Re: [PATCH 3/5] Bluetooth: create a l2cap dir
Date: Tue, 13 Jul 2010 14:13:48 -0300 [thread overview]
Message-ID: <1279041228.6282.20.camel@localhost.localdomain> (raw)
In-Reply-To: <1279033035-24708-3-git-send-email-gustavo@padovan.org>
Hi Gustavo,
> The dir is being created looking forward to the l2cap.c split.
>
> Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
> ---
> net/bluetooth/Makefile | 2 +-
> net/bluetooth/l2cap.c | 4859 ------------------------------------------
> net/bluetooth/l2cap/Makefile | 5 +
> net/bluetooth/l2cap/l2cap.c | 4859 ++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 4865 insertions(+), 4860 deletions(-)
> delete mode 100644 net/bluetooth/l2cap.c
> create mode 100644 net/bluetooth/l2cap/Makefile
> create mode 100644 net/bluetooth/l2cap/l2cap.c
hold off with this changes. We are not doing a separate directory
anyway. I need more time to think about it.
Regards
Marcel
next prev parent reply other threads:[~2010-07-13 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 14:57 [PATCH 1/5] Bluetooth: Add Copyright notice to L2CAP Gustavo F. Padovan
2010-07-13 14:57 ` [PATCH 2/5] Bluetooth: update L2CAP version Gustavo F. Padovan
2010-07-13 14:57 ` [PATCH 3/5] Bluetooth: create a l2cap dir Gustavo F. Padovan
2010-07-13 14:57 ` [PATCH 4/5] Bluetooth: Prepare l2cap for split Gustavo F. Padovan
2010-07-13 14:57 ` [PATCH 5/5] Bluetooth: first move for L2CAP split Gustavo F. Padovan
2010-07-13 17:13 ` Marcel Holtmann [this message]
2010-07-15 20:03 ` [PATCH 3/5] Bluetooth: create a l2cap dir Gustavo F. Padovan
2010-07-13 17:12 ` [PATCH 2/5] Bluetooth: update L2CAP version Marcel Holtmann
2010-07-13 17:11 ` [PATCH 1/5] Bluetooth: Add Copyright notice to L2CAP 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=1279041228.6282.20.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).