[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150418085712.GB29858@kroah.com>
Date: Sat, 18 Apr 2015 10:57:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jens Wiklander <jens.wiklander@...aro.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
javier@...igon.com, Herbert Xu <herbert@...dor.apana.org.au>,
tpmdd-devel@...ts.sourceforge.net, valentin.manea@...wei.com,
jean-michel.delorme@...com, emmanuel.michel@...com
Subject: Re: [RFC PATCH 1/2] tee: generic TEE subsystem
On Fri, Apr 17, 2015 at 09:50:56AM +0200, Jens Wiklander wrote:
> +struct tee_device {
> + char name[TEE_MAX_DEV_NAME_LEN];
> + const struct tee_desc *desc;
> + struct device *dev;
No, please embed the device in your structure, don't have a pointer to
it.
> + struct miscdevice miscdev;
This can be a pointer, as the lifecycle of your device is not dictated
by the miscdevice, but rather the 'struct device'.
> +
> + void *driver_data;
You don't need this, use 'struct device''s pointer instead.
> +
> + struct list_head list_shm;
> + struct tee_shm_pool *pool;
> +};
--
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/
Powered by blists - more mailing lists