From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: where can I find patch for 2.6.9?
Date: Fri, 04 Feb 2005 18:31:23 +0100 [thread overview]
Message-ID: <1107538283.6921.51.camel@pegasus> (raw)
In-Reply-To: <4203A9C4.7040509@gmx.ch>
Hi Marco,
> So the 2.4.x patches are all up2date and have the same fixes as the most
> recent 2.6.x one?
not quite right. All 2.4 patches provide the same level of the Bluetooth
subsystem, but this is out of date if you compare it with the stuff that
are in the 2.6 kernel and its patches.
We are developing for 2.6 and I don't have time to do the backporting to
2.4 and actually I see no reason to do this. People should start using
the new stable kernel series or pay someone to backport the stuff if
they wanna stick with an old kernel.
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-02-04 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 5:05 [Bluez-users] where can I find patch for 2.6.9? Embedded System
2005-02-04 7:26 ` [Bluez-users] " Sebastian Roth
2005-02-04 9:06 ` Embedded System
2005-02-04 11:52 ` Marcel Holtmann
2005-02-04 16:58 ` Marco Trudel
2005-02-04 17:31 ` Marcel Holtmann [this message]
2005-02-04 17:39 ` Marco Trudel
2005-02-04 18:06 ` 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=1107538283.6921.51.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 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.