From: Marcel Holtmann <marcel@holtmann.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: marcel@holtmann.or, maxk@qualcomm.com, bluez-devel@lists.sf.net,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] net/bluetooth/: possible cleanups
Date: Thu, 05 May 2005 15:28:30 +0200 [thread overview]
Message-ID: <1115299710.8496.168.camel@pegasus> (raw)
In-Reply-To: <20050505002310.GF3593@stusta.de>
Hi Adrian,
> This patch contains the following possible cleanups:
> - #ifdef HCI_DATA_DUMP the following function:
> lib.c: bt_dump
> - #if 0 the following unused global functions:
> - hci_core.c: hci_suspend_dev
> - hci_core.c: hci_resume_dev
> - remove the following unneeded EXPORT_SYMBOL's:
> - hci_core.c: hci_dev_get
> - hci_core.c: hci_send_cmd
> - hci_event.c: hci_si_event
>
> Please review which of these changes do make sense and which conflict
> with pending patches.
I like to let hci_suspend_dev() and hci_resume_dev() stay for now. No
driver uses it, but actually nobody really looked deep enough to really
understand the needs for suspend of Bluetooth devices.
The hci_dev_get(), hci_send_cmd() and hci_si_event() doesn't need to be
exported. And I think that the bt_dump() and and BT_DMP() stuff can be
removed completely.
Please redo the patch and actually it is enough to copy the bluez-devel
mailing list. I will take care of getting it back into mainline.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
prev parent reply other threads:[~2005-05-05 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 0:23 [2.6 patch] net/bluetooth/: possible cleanups Adrian Bunk
2005-05-05 13:28 ` 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=1115299710.8496.168.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.or \
--cc=maxk@qualcomm.com \
--cc=netdev@oss.sgi.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).