From: Marcel Holtmann <marcel@holtmann.org>
To: "Robert M. Stockmann" <stock@stokkie.net>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Hannes Reinecke <hare@suse.de>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@redhat.com>
Subject: Re: udev bluez
Date: Tue, 20 Jun 2006 18:47:41 +0200 [thread overview]
Message-ID: <1150822061.18381.50.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0606201759140.11776-100000@hubble.stokkie.net>
Hi Robert,
> It seems the story of the greatest piece of software ever written
> is being hit by the bluez of having to support too many seperate
> addon hardware devices, which the coders themselves in many cases
> never heard of. Until the udev problems showup.
you almost got my attention :)
Be careful with the word BlueZ, because this is the codename of the
Bluetooth subsystem/stack for Linux.
Regards
Marcel
next prev parent reply other threads:[~2006-06-20 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 16:11 udev bluez Robert M. Stockmann
2006-06-20 16:47 ` Marcel Holtmann [this message]
2006-06-20 17:39 ` Alan Cox
2006-06-21 12:06 ` Kay Sievers
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=1150822061.18381.50.camel@localhost \
--to=marcel@holtmann.org \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=hare@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stock@stokkie.net \
--cc=torvalds@osdl.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