linux-kernel - Re: Clarifying platform_device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1207397253.5021.23.camel@dax.rpnet.com>
Date:	Sat, 05 Apr 2008 13:07:33 +0100
From:	Richard Purdie <rpurdie@...ys.net>
To:	Jaya Kumar <jayakumar.lkml@...il.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Clarifying platform_device_unregister

On Tue, 2008-04-01 at 21:57 -0400, Jaya Kumar wrote:
> I also have a followup. Does corgi/spitz_pm need to manage the module
> refcount of sharpsl-pm? I couldn't find any platform device code that
> manages the refcount of the platform driver that it binds them to. So
> I suspect this means that platform devices must do the try_module_get
> stuff themselves. Out of curiosity, what's the reason for not doing
> this inside the base/platform.c code?

I don't think any refcount is needed since corgi/spitz_pm refer to
functions in sharpsl-pm and therefore sharpsl-pm will always be around
as long as corgi/spitz_pm is.

Regards,

Richard

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/