From: Matt Mackall <mpm@selenic.com>
To: Arne Caspari <arne@datafloater.de>
Cc: linux-kernel@vger.kernel.org, Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [PATCH] drivers/base/driver.c : driver_unregister
Date: Mon, 13 Dec 2004 13:07:33 -0800 [thread overview]
Message-ID: <20041213210733.GD12189@waste.org> (raw)
In-Reply-To: <41BD42E6.6000402@datafloater.de>
On Mon, Dec 13, 2004 at 08:21:10AM +0100, Arne Caspari wrote:
> Arne Caspari wrote:
> >Russell King wrote:
> >>No. The semaphore is there to ensure that the function does not
> >>return until the driver structure has a use count of zero. If you
> >>tested your patch, you'd find that your change would deadlock on
> >>the locked semaphore.
> >
> >I am sorry I can not test that patch since unloading of the modules I am
> >currently testing blocks anyway. This makes it very hard to test the
> >patch :-( and currently this was the reason why I was going to this.
>
> I reverted the code to the original 2.6.9 and unloading of IEEE1394
> modules like 'eth1394' does just that: It deadlocks on this semaphore.
>
> At least this is a good excuse why I was not able to test my patch ;-)
> The behaviour just remained the same as before...
>
> Btw. I am developing/debugging on a machine without serial/parallel
> ports. Is there a way to connect a kernel mode debugger to this. I am
> used to windows development and there the debugger works on a IEEE1394
> connection. Does anybody have hints to improve development on such a
> machine?
Netconsole, and/or kgdb-over-ethernet? You'll need a -mm or -tiny
kernel for the latter, or just pull the patches individually.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2004-12-13 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 18:54 [PATCH] drivers/base/driver.c : driver_unregister Arne Caspari
2004-12-11 19:11 ` Russell King
2004-12-11 19:24 ` Arne Caspari
2004-12-13 7:21 ` Arne Caspari
2004-12-13 21:07 ` Matt Mackall [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=20041213210733.GD12189@waste.org \
--to=mpm@selenic.com \
--cc=arne@datafloater.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).