From: Marcel Holtmann <marcel@holtmann.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Switching the Logitech-Hub
Date: Mon, 05 Jan 2004 02:49:59 +0100 [thread overview]
Message-ID: <1073267399.3804.8.camel@pegasus> (raw)
In-Reply-To: <8600000.1073220340@[192.168.207.2]>
Hi Alexander,
> I've got no comments, it's not surprising, it's just 8 hours on this list.
> But I also have looked through the sources and up to now, I don't see, why
> this should break other devices. And it seems there are some more people
> with the same problem. e.g.
> http://sourceforge.net/mailarchive/forum.php?thread_id=3345181&forum_id=5398
>
> I assume there are also some more who are wondering why sending reports
> using hiddev doesn't work. But not everyone will find the reason. Without
> your help, I wouldn't have find it too.
>
> As the author from the patch writes, it doesn't seem to interrest anyone
> from the usb-devels.
it is a good idea to repost a clean patch for 2.4 and 2.6 to the Linux
USB developer mailing list. Turn the attention to the problem.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-01-05 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 5:23 [Bluez-devel] Switching the Logitech-Hub Alexander Holler
2004-01-04 10:40 ` Marcel Holtmann
2004-01-04 12:45 ` Alexander Holler
2004-01-05 1:49 ` 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=1073267399.3804.8.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=holler@ahsoftware.de \
/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