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 10:28:29 +0200 [thread overview]
Message-ID: <1123144109.8331.58.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.33.0508041007340.7461-100000@redbean.intranet.gw-instruments.de>
Hi Peter,
> BTW (now for something completly different) : we had some trouble with our
> PCI driver. Can you tell me when you introduced hci_alloc_dev () ??? This
> is just for backward compatibility for the modified driver.
I am not 100% sure, but my patches say that 2.6.4 was the first kernel
with the dynamic allocated hci_dev structure.
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
next prev parent reply other threads:[~2005-08-04 8:28 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 [this message]
2005-08-04 8:54 ` Peter Wippich
2005-08-04 9:05 ` 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=1123144109.8331.58.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