Linux bluetooth development
 help / color / mirror / Atom feed
From: fabien.proriolpatch@kazoe.org
To: linux-bluetooth@vger.kernel.org
Cc: Fabien Proriol <fabien.proriol@jdsu.com>
Subject: [PATCH BlueZ] Fix obex protocol for powerpc
Date: Tue, 26 Jul 2016 15:22:49 +0200	[thread overview]
Message-ID: <1469539369-17245-2-git-send-email-fabien.proriolpatch@kazoe.org> (raw)
In-Reply-To: <1469539369-17245-1-git-send-email-fabien.proriolpatch@kazoe.org>

From: Fabien Proriol <fabien.proriol@jdsu.com>

omtu and imtu is define as uint16_t in l2cap_get function (use with va_arg).

Signed-off-by: Fabien Proriol <fabien.proriol@jdsu.com>
---
 obexd/plugins/bluetooth.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/obexd/plugins/bluetooth.c b/obexd/plugins/bluetooth.c
index d8b872a..3ee5432 100644
--- a/obexd/plugins/bluetooth.c
+++ b/obexd/plugins/bluetooth.c
@@ -75,8 +75,8 @@ static void connect_event(GIOChannel *io, GError *err, void *user_data)
 	struct bluetooth_profile *profile = user_data;
 	struct obex_server *server = profile->server;
 	int type;
-	int omtu = BT_TX_MTU;
-	int imtu = BT_RX_MTU;
+	uint16_t omtu = BT_TX_MTU;
+	uint16_t imtu = BT_RX_MTU;
 	gboolean stream = TRUE;
 	socklen_t len = sizeof(int);
 
-- 
2.7.3

  reply	other threads:[~2016-07-26 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 13:22 [PATCH BlueZ] Fix obex protocol for powerpc fabien.proriolpatch
2016-07-26 13:22 ` fabien.proriolpatch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-28 13:12 fabien.proriolpatch
2016-07-28 13:12 ` fabien.proriolpatch
2016-07-28 14:00   ` Fabien PRORIOL
2016-07-28 14:06 fabien.proriolpatch
2016-07-28 14:06 ` fabien.proriolpatch
2016-07-29 11:02   ` Luiz Augusto von Dentz

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=1469539369-17245-2-git-send-email-fabien.proriolpatch@kazoe.org \
    --to=fabien.proriolpatch@kazoe.org \
    --cc=fabien.proriol@jdsu.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