From: Zhenhua Zhang <zhenhua.zhang@intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 3/4] btio: Remove unused bt_io_set function
Date: Thu, 9 Sep 2010 17:41:22 +0800 [thread overview]
Message-ID: <1284025283-3773-4-git-send-email-zhenhua.zhang@intel.com> (raw)
In-Reply-To: <1284025283-3773-1-git-send-email-zhenhua.zhang@intel.com>
It is not used by either obex or bluez.
---
btio/btio.c | 33 ---------------------------------
btio/btio.h | 3 ---
2 files changed, 0 insertions(+), 36 deletions(-)
diff --git a/btio/btio.c b/btio/btio.c
index 42a3bcd..d4969e5 100644
--- a/btio/btio.c
+++ b/btio/btio.c
@@ -1074,39 +1074,6 @@ gboolean bt_io_accept(GIOChannel *io, BtIOConnect connect, void *user_data,
return TRUE;
}
-gboolean bt_io_set(GIOChannel *io, BtIOType type, GError **err,
- BtIOOption opt1, ...)
-{
- va_list args;
- gboolean ret;
- struct set_opts opts;
- int sock;
-
- va_start(args, opt1);
- ret = parse_set_opts(&opts, err, opt1, args);
- va_end(args);
-
- if (!ret)
- return ret;
-
- sock = g_io_channel_unix_get_fd(io);
-
- switch (type) {
- case BT_IO_L2RAW:
- case BT_IO_L2CAP:
- return l2cap_set(sock, opts.sec_level, opts.imtu, opts.omtu,
- opts.mode, opts.master, err);
- case BT_IO_RFCOMM:
- return rfcomm_set(sock, opts.sec_level, opts.master, err);
- case BT_IO_SCO:
- return sco_set(sock, opts.mtu, err);
- }
-
- g_set_error(err, BT_IO_ERROR, BT_IO_ERROR_INVALID_ARGS,
- "Unknown BtIO type %d", type);
- return FALSE;
-}
-
gboolean bt_io_get(GIOChannel *io, BtIOType type, GError **err,
BtIOOption opt1, ...)
{
diff --git a/btio/btio.h b/btio/btio.h
index e9dcc9f..3c5db2a 100644
--- a/btio/btio.h
+++ b/btio/btio.h
@@ -79,9 +79,6 @@ typedef void (*BtIOConnect)(GIOChannel *io, GError *err, void *user_data);
gboolean bt_io_accept(GIOChannel *io, BtIOConnect connect, void *user_data,
GDestroyNotify destroy, GError **err);
-gboolean bt_io_set(GIOChannel *io, BtIOType type, GError **err,
- BtIOOption opt1, ...);
-
gboolean bt_io_get(GIOChannel *io, BtIOType type, GError **err,
BtIOOption opt1, ...);
--
1.7.0.4
next prev parent reply other threads:[~2010-09-09 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 9:41 obex: isolate btio.[ch] as a library and do some cleanup Zhenhua Zhang
2010-09-09 9:41 ` [PATCH 1/4] btio: Remove blank line at EOF Zhenhua Zhang
2010-09-09 9:41 ` [PATCH 2/4] btio: Seperate btio.[ch] into btio directory Zhenhua Zhang
2010-09-09 9:41 ` Zhenhua Zhang [this message]
2010-09-09 10:38 ` [PATCH 3/4] btio: Remove unused bt_io_set function Johan Hedberg
2010-09-10 0:11 ` Zhang, Zhenhua
2010-09-09 9:41 ` [PATCH 4/4] btio: Replace void * with gpointer Zhenhua Zhang
-- strict thread matches above, loose matches on Subject: below --
2010-09-09 9:43 bluez: isolate btio.[ch] as a library and do cleanup Zhenhua Zhang
2010-09-09 9:43 ` [PATCH 3/4] btio: Remove unused bt_io_set function Zhenhua Zhang
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=1284025283-3773-4-git-send-email-zhenhua.zhang@intel.com \
--to=zhenhua.zhang@intel.com \
--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