I'm not quite happy with that patch. Specifically, I see a risk of
module_put being called too often.
Could you explain in some more detail what bug you are trying to fix?
Do you have a sequence of events which leads to a situation where the
bas_gigaset module cannot be unloaded but should be?
I've tried to reproduce the problem doing various tests -- but without
Then i've checked the code and there was already this fix:
commit e468c04894f36045cf93d1384183a461014b6840 (Gigaset: permit module unload)
This was commited after 2.6.24 was released.
And (shit happens!) on the machine where I've previously tested the
stuff I had also an 2.6.24 kernel installed.
So it seems that I have mixed up different kernel versions when I've
tested my patch. Because with current git-tree bas_gigaset can be
unloaded without any problems.
Sorry for the noise.
No problem. Thanks for the feedback.
Tilman Schmidt E-Mail: firstname.lastname@example.org
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge=F6ffnet mindestens haltbar bis: (siehe R=FCckseite)