From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Kernel Oops on 2.6.23-rc6
Date: Sat, 22 Sep 2007 21:11:39 +0200 [thread overview]
Message-ID: <46F568EB.2090806@idlum.be> (raw)
In-Reply-To: <1190447455.5133.55.camel@aeonflux.holtmann.net>
Hi Marcel,
> please post this to LKML, because it looks like an issue withing the
> device_move() API call.
Ok, will do. Do you think they may need more information about anything,
or is this report complete enough for them to be useful?
Best Regards,
Pierre-Yves
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-09-22 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 18:31 [Bluez-devel] Kernel Oops on 2.6.23-rc6 Pierre-Yves Paulus
2007-09-22 7:50 ` Marcel Holtmann
2007-09-22 19:11 ` Pierre-Yves Paulus [this message]
2007-09-23 6:27 ` 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=46F568EB.2090806@idlum.be \
--to=py@idlum.be \
--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