From: Jes Sorensen <jes.soren...@redhat.com> min_size/max_size aren't used anywhere, and they were just causing headaches in the drivers being ported over to the new interfaces.
Signed-off-by: Jes Sorensen <jes.soren...@redhat.com> Signed-off-by: Benjamin Romer <benjamin.ro...@unisys.com> --- drivers/staging/unisys/include/visorbus.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/unisys/include/visorbus.h b/drivers/staging/unisys/include/visorbus.h index 581d962..e4a21e4 100644 --- a/drivers/staging/unisys/include/visorbus.h +++ b/drivers/staging/unisys/include/visorbus.h @@ -59,8 +59,6 @@ struct visorchipset_state { struct visor_channeltype_descriptor { const uuid_le guid; const char *name; - unsigned long min_size; - unsigned long max_size; }; /** Information provided by each visor driver when it registers with the -- 2.1.4 _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel