From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Microsoft IntelliMouse with kernel 2.6.1 and patch-2.6.18-mh1 is broken (fix provided)
Date: Fri, 29 Sep 2006 13:52:35 +0200 [thread overview]
Message-ID: <1159530755.6131.34.camel@localhost> (raw)
In-Reply-To: <451A35A1.6020309@brainhub.org>
Hi Andrey,
> here is the patch against linux-2.6.18-mh1 to fix
> IntelliMouse. That's the best range of changes I have time to provide:
> somewhere in these changes IntelliMouse was broken. I believe this
> happened between patch-2.6.15-mh2 and linux-2.6.18-mh1. While there are
> a lot of changes in these 17 files, but most of them are variable
> renames. I hope this helps you to narrow down the issue.
I only care about changes in net/bluetooth/hidp/. All others are not
relevant. Can't you show me your changes from that directory.
> [ Does sending compressed patched works? Trying uncompressed first. ]
Keep them uncompressed, then I can read them in my email client.
Regards
Marcel
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-09-29 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 6:29 [Bluez-users] Microsoft IntelliMouse with kernel 2.6.18 and patch-2.6.18-mh1 is broken (fix provided) Andrey Jivsov
2006-09-27 7:52 ` Marcel Holtmann
2006-09-27 8:26 ` [Bluez-users] Microsoft IntelliMouse with kernel 2.6.1 " Andrey Jivsov
2006-09-29 11:52 ` Marcel Holtmann [this message]
2006-09-29 17:58 ` Andrey Jivsov
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=1159530755.6131.34.camel@localhost \
--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