There doesn't appear any good reason to mark NVMEM cdevs as DEVFS_IS_CHARACTER_DEV, since NVMEM devices should be able to read/write data at arbitrary offsets and are not different from any other cdevs representing non-volatile storage. Signed-off-by: Andrey Smirnov <andrew.smirnov@xxxxxxxxx> --- drivers/nvmem/core.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c index 63c0f997b..9fd599095 100644 --- a/drivers/nvmem/core.c +++ b/drivers/nvmem/core.c @@ -96,7 +96,6 @@ static int nvmem_register_cdev(struct nvmem_device *nvmem, const char *name) alias = of_alias_get(dev->device_node); nvmem->cdev.name = xstrdup(alias ?: name); - nvmem->cdev.flags = DEVFS_IS_CHARACTER_DEV; nvmem->cdev.ops = &nvmem_chrdev_ops; nvmem->cdev.dev = &nvmem->dev; nvmem->cdev.size = nvmem->size; -- 2.20.1 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
