From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] kernel 2.6.16 and bluez stack patches
Date: Mon, 05 Jun 2006 16:17:04 +0200 [thread overview]
Message-ID: <1149517024.7696.14.camel@localhost> (raw)
In-Reply-To: <1149462584.13066.2.camel@neutrino.cosmos.net>
Hi Didier,
> Since months I wait for the patch to have a good bluez stack in the
> kernel 2.6.16 and nothing ...
what do you mean with "good bluez stack" the vanilla 2.6.16 kernel is
pretty good.
> I've read at some places to apply the patch for 2.6.15 but a lot of diff
> don't apply at all, and another place tell us that the main kernel tree
> is up to date ?
I think that I actually already fixed that, but never came around to
release another -mh patch.
Regards
Marcel
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-05 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 23:09 [Bluez-users] kernel 2.6.16 and bluez stack patches Didier LINK
2006-06-05 14:17 ` Marcel Holtmann [this message]
2006-06-05 15:36 ` Didier LINK
2006-06-05 15:37 ` Marcel Holtmann
2006-06-05 15:50 ` Didier LINK
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=1149517024.7696.14.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.