From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Installing Bluez
Date: Fri, 28 Jan 2005 18:39:55 +0100 [thread overview]
Message-ID: <1106933995.9644.5.camel@pegasus> (raw)
In-Reply-To: <41FA486F.9040000@gmx.ch>
Hi Marco,
> I expect it to pe for the 2.6.10 Kernel and hope that it's usuable with the
> 2.6.7 one...
> How bad is the 2.6.7 patch? Wher can I download it?
the latest 2.6.7 patch includes almost the same of the Bluetooth
subsystem that is in 2.6.8. So you miss the patches for two kernel
releases and actually I counted them. There are 33 patches between the
2.6.7 and 2.6.10 kernel. The ones from the patch-2.6.10-mh2 are not
included in this count.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-28 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 22:14 [Bluez-users] Installing Bluez Marco Trudel
2005-01-26 22:24 ` Marcel Holtmann
2005-01-26 22:54 ` Marco Trudel
2005-01-27 17:32 ` Marcel Holtmann
2005-01-28 14:13 ` Marco Trudel
2005-01-28 17:39 ` Marcel Holtmann [this message]
2005-01-28 6:15 ` [Bluez-users] Workaround for the bug in gnu arm linker while using sdpd program Heejune AHN
2005-01-28 7:42 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 9:27 [Bluez-users] Installing BlueZ ronny hidayat
2005-09-30 12:09 ` Marcel Holtmann
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=1106933995.9644.5.camel@pegasus \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).