From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Patch for L2CAP (kernel<->userspace)
Date: Wed, 13 Apr 2005 16:19:40 +0200 [thread overview]
Message-ID: <1113401980.9061.34.camel@pegasus> (raw)
In-Reply-To: <loom.20050413T154320-783@post.gmane.org>
Hi Matthias,
> The solution is, that "a patch for that problem is needed so that for commands
> from the RAW socket no responses are send." ("However I looked at the code
> and it seems that the the kernel respond to packets with all idents. It should
> not do that, because they are shared between the kernel and the userspace.")
>
> Since iam a noob programmer i want to ask, if the problem is already fixed in
> a newer patch or is the problem still existent.
I thought about fixing this, but at the moment it isn't done. Feel free
to send in a patch for it, because I am busy with other stuff and the
whole SCM/Bitkeeper/GIT thing is not really helping right now.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-04-13 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:53 [Bluez-devel] Patch for L2CAP (kernel<->userspace) Matthias
2005-04-13 14:19 ` 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=1113401980.9061.34.camel@pegasus \
--to=marcel@holtmann.org \
--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