From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] problems with patch for 2.6.10...
Date: Wed, 26 Jan 2005 18:33:29 +0100 [thread overview]
Message-ID: <1106760809.28444.39.camel@pegasus> (raw)
In-Reply-To: <1106739703.6665.5.camel@localhost.localdomain>
Hi Rob,
> I've just applied the latest patch ( 2.6.10-mh2 ) to the latest
> available kernel source for Fedora Core 3 from their update site (2.6.10
> with a few patches applied). All was well except that a patch for the
> Makefile was rejected due to the EXTRAVERSION flag being different.
> Everything built and installed perfectly, but now I'm getting the
> following on bootup. I've also upgraded the stock bluez-libs and bluez-
> utils rpms for FC3 with the latest from the bluez.org site.
use a vanilla 2.6.10, because the -mh patches are not made to work with
any distribution kernels. If they do feel happy, if not, blame them.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-01-26 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 11:41 [Bluez-devel] problems with patch for 2.6.10 Robert Foster
2005-01-26 17:33 ` 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=1106760809.28444.39.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