From: Oliver Hartkopp <oliver@hartkopp.net>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: possible recursive locking in 2.6.30-rc6
Date: Wed, 27 May 2009 07:52:04 +0200 [thread overview]
Message-ID: <4A1CD504.9090202@hartkopp.net> (raw)
In-Reply-To: <a8e1da0905261813i3577af33g101336259a51c03c@mail.gmail.com>
Dave Young wrote:
>
> Hi oliver
>
> Could you try the attached patch and report your result?
>
Hi Dave,
that fixed the problem!
BT DUN is working properly again. Many thanks!
Tested-by: Oliver Hartkopp <oliver@hartkopp.net>
Best regards,
Oliver
next prev parent reply other threads:[~2009-05-27 5:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 13:29 possible recursive locking in 2.6.30-rc6 Oliver Hartkopp
2009-05-25 19:55 ` Oliver Hartkopp
2009-05-26 8:19 ` Oliver Hartkopp
2009-05-27 1:13 ` Dave Young
2009-05-27 5:52 ` Oliver Hartkopp [this message]
2009-05-27 6:27 ` Marcel Holtmann
2009-05-27 7:42 ` Marcel Holtmann
2009-05-27 11:11 ` Dave Young
2009-05-27 11:17 ` Oliver Hartkopp
2009-05-28 0:42 ` Dave Young
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=4A1CD504.9090202@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=hidave.darkstar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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