From: Marcel Holtmann <marcel@holtmann.org>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 1/6] Bluetooth: Remove most of the inline usage
Date: Wed, 23 May 2012 13:11:57 +0200 [thread overview]
Message-ID: <1337771517.15105.77.camel@aeonflux> (raw)
In-Reply-To: <1337756663-19805-1-git-send-email-gustavo@padovan.org>
Hi Gustavo,
> Only obvious cases were left as inline, mostly oneline functions.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
> net/bluetooth/bnep/core.c | 4 +-
> net/bluetooth/bnep/netdev.c | 6 +-
> net/bluetooth/hci_core.c | 33 +++++-----
> net/bluetooth/hci_event.c | 144 ++++++++++++++++++-------------------------
> net/bluetooth/hci_sock.c | 6 +-
> net/bluetooth/hidp/core.c | 4 +-
> net/bluetooth/mgmt.c | 2 +-
> net/bluetooth/rfcomm/core.c | 18 +++---
> net/bluetooth/rfcomm/tty.c | 4 +-
> net/bluetooth/sco.c | 9 +--
> 10 files changed, 104 insertions(+), 126 deletions(-)
all 6 patches have been applied to bluetooth-next tree.
However we need to watch out for some of these include removal since in
some cases there are still needed on non-x86 platforms.
Regards
Marcel
prev parent reply other threads:[~2012-05-23 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 7:04 [PATCH 1/6] Bluetooth: Remove most of the inline usage Gustavo Padovan
2012-05-23 7:04 ` [PATCH 2/6] Bluetooth: Remove 'register' usage from the subsystem Gustavo Padovan
2012-05-23 7:04 ` [PATCH 3/6] Bluetooth: Fix coding style in include/net/bluetooth Gustavo Padovan
2012-05-23 7:04 ` [PATCH 4/6] Bluetooth: Fix coding style in the subsystem Gustavo Padovan
2012-05-23 7:04 ` [PATCH 5/6] Bluetooth: Remove unnecessary headers include Gustavo Padovan
2012-05-23 7:04 ` [PATCH 6/6] Bluetooth: Remove unneeded EXPORT_SYMBOL Gustavo Padovan
2012-05-23 11:11 ` Marcel Holtmann [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=1337771517.15105.77.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--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