From: Valentin SURREL <dev@surrel.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] PATCH for dund : correct --dialup behavior (Tomtom GPS)
Date: Sun, 19 Nov 2006 12:31:41 +0100 [thread overview]
Message-ID: <4560409D.8040001@surrel.org> (raw)
In-Reply-To: <1163934784.11790.0.camel@localhost>
Marcel Holtmann a =E9crit :
> Hi Valentin,
>
> please create a unified diff, because I can't read these context diffs.
>
> Regards
>
> Marcel
>
> =
Hi,
It's my really first contribution to the GPL world, and I'm not familiar =
with the developpment tools. :-)
This one might be better... (it works for me with "patch < mypatch" in =
the correct directory)
--- sdp.c 2006-05-23 14:48:37.000000000 +0200
+++ sdp.c 2006-11-19 11:37:10.000000000 +0100
@@ -171,6 +171,9 @@ int dun_sdp_search(bdaddr_t *src, bdaddr
case ACTIVESYNC:
sdp_uuid128_create(&svclass, (void *) async_uuid);
break;
+ case DIALUP:
+ sdp_uuid16_create(&svclass, DIALUP_NET_SVCLASS_ID);
+ break;
default:
sdp_uuid16_create(&svclass, LAN_ACCESS_SVCLASS_ID);
break;
Valentin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-19 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:04 [Bluez-devel] PATCH for dund : correct --dialup behavior (Tomtom GPS) Valentin SURREL
2006-11-19 11:13 ` Marcel Holtmann
2006-11-19 11:31 ` Valentin SURREL [this message]
2006-11-20 8:16 ` Marcel Holtmann
[not found] <mailman.55247.1163941931.8777.bluez-devel@lists.sourceforge.net>
2006-11-19 13:27 ` Arjan van de Ven
2006-11-20 8:17 ` 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=4560409D.8040001@surrel.org \
--to=dev@surrel.org \
--cc=bluez-devel@lists.sourceforge.net \
/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