From: Johannes Hoerhan <jhoe@aon.at>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm kernel 2.6.19 probs
Date: Tue, 19 Dec 2006 01:25:01 +0100 [thread overview]
Message-ID: <4587315D.10703@aon.at> (raw)
In-Reply-To: <loom.20061218T215536-830@post.gmane.org>
Hi, I am also using udev 103 - I did not check the udev events. With my
patch everything is working great now. If the information is needed I
will monitor udev with the non working version of tty.c.
joho
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-19 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 15:04 [Bluez-devel] rfcomm kernel 2.6.19 probs johannes hoerhan
2006-12-17 12:47 ` Marcel Holtmann
2006-12-18 21:04 ` Markus Uhr
2006-12-19 0:25 ` Johannes Hoerhan [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=4587315D.10703@aon.at \
--to=jhoe@aon.at \
--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