From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] crazy mouse
Date: Sun, 11 Jun 2006 15:41:33 +0200 [thread overview]
Message-ID: <1150033293.21858.1.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1150017892.13788.1.camel@neutrino.cosmos.net>
Hi Didier,
> > please use 2.6.16-mh1 and the attached patch. That should make it work
> > again as expected.
>
> Yes, it works perfect now ! Thanks a lot ! :)
and here comes 2.6.16-mh3 :)
Regards
Marcel
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-06-11 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 21:42 [Bluez-users] crazy mouse Didier LINK
2006-06-05 21:57 ` Marcel Holtmann
2006-06-06 17:46 ` Didier LINK
2006-06-06 20:37 ` Ulisses Furquim
2006-06-08 20:26 ` Didier LINK
2006-06-09 1:14 ` Ulisses Furquim
2006-06-09 20:38 ` Didier LINK
2006-06-11 0:35 ` Marcel Holtmann
2006-06-11 9:24 ` Didier LINK
2006-06-11 13:41 ` 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=1150033293.21858.1.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@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