From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DUN lookup on Samsung D500 raises SIGSEGV
Date: Thu, 04 Aug 2005 11:05:02 +0200 [thread overview]
Message-ID: <1123146302.8331.62.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.33.0508041049030.7461-100000@redbean.intranet.gw-instruments.de>
Hi Peter,
> ok, this seems to be far enough ago to keep it as the standard version.
> If someone wants to compile it with an older kernel it will fail anyway.
at the OLS the network guys told me that the internals of sk_buff would
change in 2.6.14 and that pkt_type will be reduced and we can't use it
anymore. I already have a patch for all drivers in the kernel source to
deal with that and you might keep an eye on it too.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-04 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 13:10 [Bluez-devel] DUN lookup on Samsung D500 raises SIGSEGV Pedro Monjo Florit
2005-08-03 17:12 ` Peter Wippich
2005-08-03 17:46 ` Steven Singer
2005-08-03 18:38 ` Marcel Holtmann
2005-08-03 18:35 ` Marcel Holtmann
2005-08-04 8:11 ` Peter Wippich
2005-08-04 8:28 ` Marcel Holtmann
2005-08-04 8:54 ` Peter Wippich
2005-08-04 9:05 ` 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=1123146302.8331.62.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 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.