pcmcia: Removed unused variable control.
PATCH 1/1 pcmcia: Removed unused variable control.
From: "Souptick Joarder (HPE)" <[email protected]>
Kernel test robot throws below warning -> drivers/pcmcia/omap_cf.c:127:7: warning: variable 'control' set but not used [-Wunused-but-set-variable]
Removed unused variable control.
--- drivers/pcmcia/omap_cf.c | 2 -- 1 file changed, 2 deletions(-)
drivers/pcmcia/omap_cf.c +0 -2
@@ -124,7 +124,6 @@ static int omap_cf_get_status(struct pcmcia_socket *s, u_int *sp)static int omap_cf_set_socket (struct pcmcia_socket *sock,struct socket_state_t *s) { -u16 control;/* REVISIT some non-OSK boards may support power switching */ switch (s->Vcc) {
@@ -135,7 +134,6 @@ omap_cf_set_socket(struct pcmcia_socket *sock, struct socket_state_t *s)return -EINVAL ; } - control =omap_readw (CF_CONTROL );if (s->flags &SS_RESET )omap_writew (CF_CONTROL_RESET ,CF_CONTROL );else
Signature · 1 line
2.25.1
Dominik Brodowski
maintainerAm Mon, Jul 25, 2022 at 06:59:55AM +0530 schrieb Souptick Joarder:
Quoted 7 lines
From: "Souptick Joarder (HPE)" <[email protected]>
Kernel test robot throws below warning ->
drivers/pcmcia/omap_cf.c:127:7: warning: variable 'control' set but not used [-Wunused-but-set-variable]Removed unused variable control.
From a code-generation standpoint, this is obiously correct, and probably the compiler removes that omap_readw() already. But, to be honest, I'm not perfectly sure on what the device expects -- and whether it's required to write back the control register (or parts of it). Does anyone still have the hardware (or specs)? If not, I'm tempted to apply this patch on the basis that the compiler might remove that omap_readw() anyway.
Thanks,
Dominik
Quoted 11 lines · Dominik Brodowski
Am Mon, Jul 25, 2022 at 06:59:55AM +0530 schrieb Souptick Joarder:
Quoted 7 lines
From: "Souptick Joarder (HPE)" <[email protected]>
Kernel test robot throws below warning ->
drivers/pcmcia/omap_cf.c:127:7: warning: variable 'control' set but not used [-Wunused-but-set-variable]Removed unused variable control.
From a code-generation standpoint, this is obiously correct, and probably the compiler removes that
omap_readw()already.
omap_readw() is an 'extern' function, so it does not get removed.
Even if it was inline, it's still "and volatile" read that gets left in because it may (and probably does) have side-effects.
Quoted 5 lines
But, to be honest, I'm not
perfectly sure on what the device expects -- and whether it's required to write back the control register (or parts of it). Does anyone still have the hardware (or specs)? If not, I'm tempted to apply this patch on the basis that the compiler might remove thatomap_readw()anyway.
I think assigning to an unused variable was at some point needed to avoid a compiler warning because otherwise omap_readw() was just a pointer dereference. The safe way to transform the code should be to drop the variable but leave the function call.
Note that the driver is only used on the 'osk' reference board, not on any devices that were in mass-production.
Arnd
Dominik Brodowski
maintainerAm Fri, Sep 23, 2022 at 08:58:47AM +0200 schrieb Arnd Bergmann:
Quoted 24 lines · Dominik Brodowski
Quoted 11 lines
Am Mon, Jul 25, 2022 at 06:59:55AM +0530 schrieb Souptick Joarder:
Quoted 7 lines
From: "Souptick Joarder (HPE)" <[email protected]>
Kernel test robot throws below warning ->
drivers/pcmcia/omap_cf.c:127:7: warning: variable 'control' set but not used [-Wunused-but-set-variable]Removed unused variable control.
From a code-generation standpoint, this is obiously correct, and probably the compiler removes that
omap_readw()already.
omap_readw()is an 'extern' function, so it does not get removed.Even if it was inline, it's still "and volatile" read that gets left in because it may (and probably does) have side-effects.
Quoted 5 lines
But, to be honest, I'm not
perfectly sure on what the device expects -- and whether it's required to write back the control register (or parts of it). Does anyone still have the hardware (or specs)? If not, I'm tempted to apply this patch on the basis that the compiler might remove thatomap_readw()anyway.
Quoted 7 lines
I think assigning to an unused variable was at some point needed to avoid a compiler warning because otherwise
omap_readw()was just a pointer dereference. The safe way to transform the code should be to drop the variable but leave the function call.Note that the driver is only used on the 'osk' reference board, not on any devices that were in mass-production.
Thanks for the evaluation, Arnd! So here's what I intend to push upstream:
From: "Souptick Joarder (HPE)" <[email protected]>
Kernel test robot throws below warning -> drivers/pcmcia/omap_cf.c:127:7: warning: variable 'control' set but not used [-Wunused-but-set-variable]
Removed unused variable control.
drivers/pcmcia/omap_cf.c +1 -3
@@ -124,8 +124,6 @@ static int omap_cf_get_status(struct pcmcia_socket *s, u_int *sp)static int omap_cf_set_socket (struct pcmcia_socket *sock,struct socket_state_t *s) { -u16 control; -/* REVISIT some non-OSK boards may support power switching */ switch (s->Vcc) {case 0 :
@@ -135,7 +133,7 @@ omap_cf_set_socket(struct pcmcia_socket *sock, struct socket_state_t *s)return -EINVAL ; } - control =omap_readw (CF_CONTROL ); +omap_readw (CF_CONTROL );if (s->flags &SS_RESET )omap_writew (CF_CONTROL_RESET ,CF_CONTROL );else