Commit ebff0330 authored by Tobias Klauser's avatar Tobias Klauser Committed by Mauro Carvalho Chehab

V4L/DVB (7322): pvrusb2: Fix storage-class as per C99 spec

The C99 specification states in section 6.11.5:

The placement of a storage-class specifier other than at the
beginning of the declaration specifiers in a declaration is an
obsolescent feature.
Signed-off-by: default avatarTobias Klauser <tklauser@distanz.ch>
Signed-off-by: default avatarMike Isely <isely@pobox.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@infradead.org>
parent 794b1607
...@@ -1502,7 +1502,7 @@ struct pvr2_std_hack { ...@@ -1502,7 +1502,7 @@ struct pvr2_std_hack {
default - which can always be overridden explicitly - and if the user default - which can always be overridden explicitly - and if the user
has otherwise named a default then that default will always be used in has otherwise named a default then that default will always be used in
place of this table. */ place of this table. */
const static struct pvr2_std_hack std_eeprom_maps[] = { static const struct pvr2_std_hack std_eeprom_maps[] = {
{ /* PAL(B/G) */ { /* PAL(B/G) */
.pat = V4L2_STD_B|V4L2_STD_GH, .pat = V4L2_STD_B|V4L2_STD_GH,
.std = V4L2_STD_PAL_B|V4L2_STD_PAL_B1|V4L2_STD_PAL_G, .std = V4L2_STD_PAL_B|V4L2_STD_PAL_B1|V4L2_STD_PAL_G,
...@@ -3695,7 +3695,7 @@ static int state_update_pipeline_state(struct pvr2_hdw *hdw) ...@@ -3695,7 +3695,7 @@ static int state_update_pipeline_state(struct pvr2_hdw *hdw)
typedef int (*state_eval_func)(struct pvr2_hdw *); typedef int (*state_eval_func)(struct pvr2_hdw *);
/* Set of functions to be run to evaluate various states in the driver. */ /* Set of functions to be run to evaluate various states in the driver. */
const static state_eval_func eval_funcs[] = { static const state_eval_func eval_funcs[] = {
state_eval_pathway_ok, state_eval_pathway_ok,
state_eval_pipeline_config, state_eval_pipeline_config,
state_eval_encoder_ok, state_eval_encoder_ok,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment