On Mon, Dec 15, 2025 at 03:16:44PM +0100, Uwe Kleine-König wrote:
The tee subsystem recently got a set of dedicated functions to register (and unregister) a tee driver. Make use of them. These care for setting the driver's bus (so the explicit assignment can be dropped) and the driver owner (which is an improvement this driver benefits from).
Reviewed-by: Sumit Garg sumit.garg@oss.qualcomm.com Signed-off-by: Uwe Kleine-König u.kleine-koenig@baylibre.com
security/keys/trusted-keys/trusted_tee.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/security/keys/trusted-keys/trusted_tee.c b/security/keys/trusted-keys/trusted_tee.c index aa3d477de6db..3cea9a377955 100644 --- a/security/keys/trusted-keys/trusted_tee.c +++ b/security/keys/trusted-keys/trusted_tee.c @@ -264,7 +264,6 @@ static struct tee_client_driver trusted_key_driver = { .id_table = trusted_key_id_table, .driver = { .name = DRIVER_NAME,
.bus = &tee_bus_type,@@ -272,12 +271,12 @@ static struct tee_client_driver trusted_key_driver = { static int trusted_tee_init(void) {
- return driver_register(&trusted_key_driver.driver);
- return tee_client_driver_register(&trusted_key_driver);
} static void trusted_tee_exit(void) {
- driver_unregister(&trusted_key_driver.driver);
- tee_client_driver_unregister(&trusted_key_driver);
} struct trusted_key_ops trusted_key_tee_ops = { -- 2.47.3
Reviewed-by: Jarkko Sakkinen jarkko@kernel.org
BR, Jarkko