From: Marcel Holtmann <marcel@holtmann.org>
To: Bhatt Abhi-ABHATT <ABHISHEK.BHATT@motorola.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluez Patches for kernel v2.4
Date: Mon, 01 Nov 2004 16:25:02 +0100 [thread overview]
Message-ID: <1099322702.16247.116.camel@pegasus> (raw)
In-Reply-To: <5987A7CB1694D811A04D0002B32C289601BF3C17@il93exb05.corp.mot.com>
Hi Abhi,
one small note, please don't send HTML emails to the mailing list. The
good old ASCII ones are perfect.
> I work on kernel v2.4 and I would be interested in having some of the
> new bluez patches for kernel v2.6 applied to v2.4.
>
> I believe there are no new feature patches for kernel v2.4 and new
> features are only being developed for kernel v2.6. Is
>
> there someone out there who also works on v2.4 and if so I would like
> to know if there is a better way to put in the new
>
> kernel patches (for e.g. patch-2.6.9-mh3) to v2.4 other than manually
> putting them in.
there are some pending security and bugfix patches for the 2.4 kernel
that I may put out next week. However there is no plan to backport any
of these new features to 2.4 and actually this will consume a lot of
time (even for me) and more time for testing them. And time is money as
you know ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-11-01 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 14:41 [Bluez-devel] Bluez Patches for kernel v2.4 Bhatt Abhi-ABHATT
2004-11-01 15:25 ` 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=1099322702.16247.116.camel@pegasus \
--to=marcel@holtmann.org \
--cc=ABHISHEK.BHATT@motorola.com \
--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