linux-kernel - [RFC PATCH 0/3] Introduce init() and exit() for platform

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>] [day] [month] [year] [list]

Date:	Tue, 24 Feb 2009 17:57:26 +0200
From:	Paulius Zaleckas <paulius.zaleckas@...tonika.lt>
To:	greg@...ah.com
Cc:	s.hauer@...gutronix.de, linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/3] Introduce init() and exit() for platform_device

For changes and documentation about this fix please see:
[RFC PATCH 1/3] platform_device: add init() exit() callbacks

Other patches demonstrate how drivers can benefit from this change.

I have two questions:
1. Is init()/exit() OK? Or should I call it activate()/deactivate()?
   Other suggestions?
2. Now exit() returns nothing. Maybe it is better if it returned int?
   How to handle such exit failure?
--
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/