From: Marcel Holtmann <marcel@holtmann.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: bluez-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] net/bluetooth/: cleanups
Date: Sun, 17 Jul 2005 17:58:03 +0200 [thread overview]
Message-ID: <1121615883.22662.38.camel@pegasus> (raw)
In-Reply-To: <20050717145709.GI3613@stusta.de>
Hi Adrian,
> This patch contains the following cleanups:
> - remove BT_DMP/bt_dump
> - 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
is this the same patch you sent me last time? I still have one of your
cleanup patches in my queue. I simply was to lazy to get them back into
mainline.
Regards
Marcel
next prev parent reply other threads:[~2005-07-17 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 14:57 [2.6 patch] net/bluetooth/: cleanups Adrian Bunk
2005-07-17 15:58 ` Marcel Holtmann [this message]
2005-07-17 22:53 ` Adrian Bunk
2005-07-18 8:55 ` [Bluez-devel] usb/sco problems Victor Shcherbatyuk
2005-07-18 9:06 ` 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=1121615883.22662.38.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bunk@stusta.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.