From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Mikkelborg <andreas.mikkelborg@hjemme.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bluez oops in 2.6.3-rc4
Date: Thu, 19 Feb 2004 21:24:51 +0100 [thread overview]
Message-ID: <1077222291.2767.30.camel@pegasus> (raw)
In-Reply-To: <20040219162234.6fee88fc.andreas.mikkelborg@hjemme.no>
Hi Andreas,
> The oops occured when I started obexserver and tried to transfer a file from my mobile phone.
> The first files went ok, but then it oopsed, now it seems I can't recreate it.
have you seen this with any previous kernel versions? Is it
reproduceable?
Regards
Marcel
prev parent reply other threads:[~2004-02-19 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 15:22 Bluez oops in 2.6.3-rc4 Andreas Mikkelborg
2004-02-19 20:24 ` 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=1077222291.2767.30.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andreas.mikkelborg@hjemme.no \
--cc=linux-kernel@vger.kernel.org \
/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