linux-kernel - Re: [PATCH] ene_ub6250: Use macros for firmware names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1343167097.25735.79.camel@ejdallLaptop>
Date:	Tue, 24 Jul 2012 15:58:17 -0600
From:	Betty Dall <betty.dall@...com>
To:	Tim Gardner <tim.gardner@...onical.com>
Cc:	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, usb-storage@...ts.one-eyed-alien.net
Subject: Re: [PATCH] ene_ub6250: Use macros for firmware names

Hi Tim,

I reviewed this patch and it looks good. Once small suggestion you can
take or leave...

On Tue, 2012-07-24 at 14:31 -0600, Tim Gardner wrote:
> Advertise firmware files using MODULE_FIRMWARE macros.
> 
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: linux-usb@...r.kernel.org
> Cc: usb-storage@...ts.one-eyed-alien.net
> Signed-off-by: Tim Gardner <tim.gardner@...onical.com>
> ---
>  drivers/usb/storage/ene_ub6250.c |   26 +++++++++++++++++++-------
>  1 file changed, 19 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/usb/storage/ene_ub6250.c b/drivers/usb/storage/ene_ub6250.c
> index b28f2ad..3fec82f 100644
> --- a/drivers/usb/storage/ene_ub6250.c
> +++ b/drivers/usb/storage/ene_ub6250.c
> @@ -29,9 +29,21 @@
>  #include "protocol.h"
>  #include "debug.h"
>  
> +#define SD_INIT1_FIRMWARE "ene-ub6250/sd_init1.bin"
> +#define SD_INIT2_FIRMWARE "ene-ub6250/sd_init2.bin"
> +#define SD_RW_FIRMWARE "ene-ub6250/sd_rdwr.bin"
> +#define MS_INIT_FIRMWARE "ene-ub6250/ms_init.bin"
> +#define MSP_RW_FIRMWARE "ene-ub6250/msp_rdwr.bin"
> +#define MS_RW_FIRMWARE "ene-ub6250/ms_rdwr.bin"
> +
>  MODULE_DESCRIPTION("Driver for ENE UB6250 reader");
>  MODULE_LICENSE("GPL");
> -
> +MODULE_FIRMWARE(SD_INIT1_FIRMWARE);
> +MODULE_FIRMWARE(SD_INIT2_FIRMWARE);
> +MODULE_FIRMWARE(SD_RW_FIRMWARE);
> +MODULE_FIRMWARE(MS_INIT_FIRMWARE);
> +MODULE_FIRMWARE(MSP_RW_FIRMWARE);
> +MODULE_FIRMWARE(MS_RW_FIRMWARE);
>  
>  /*
>   * The table of devices
> @@ -1883,28 +1895,28 @@ static int ene_load_bincode(struct us_data *us, unsigned char flag)
>  	/* For SD */
>  	case SD_INIT1_PATTERN:
>  		US_DEBUGP("SD_INIT1_PATTERN\n");
> -		fw_name = "ene-ub6250/sd_init1.bin";
> +		fw_name = SD_INIT1_FIRMWARE;
>  		break;
>  	case SD_INIT2_PATTERN:
>  		US_DEBUGP("SD_INIT2_PATTERN\n");
> -		fw_name = "ene-ub6250/sd_init2.bin";
> +		fw_name = SD_INIT2_FIRMWARE;
>  		break;
>  	case SD_RW_PATTERN:
>  		US_DEBUGP("SD_RDWR_PATTERN\n");

All the other rdwr patterns are RW not RDWR. So you could change this
one to be SD_RW_PATTERN to be consistent with MSP_RW_PATTERN and
MS_RW_PATTERN.  This is a nit.

> -		fw_name = "ene-ub6250/sd_rdwr.bin";
> +		fw_name = SD_RW_FIRMWARE;
>  		break;
>  	/* For MS */
>  	case MS_INIT_PATTERN:
>  		US_DEBUGP("MS_INIT_PATTERN\n");
> -		fw_name = "ene-ub6250/ms_init.bin";
> +		fw_name = MS_INIT_FIRMWARE;
>  		break;
>  	case MSP_RW_PATTERN:
>  		US_DEBUGP("MSP_RW_PATTERN\n");
> -		fw_name = "ene-ub6250/msp_rdwr.bin";
> +		fw_name = MSP_RW_FIRMWARE;
>  		break;
>  	case MS_RW_PATTERN:
>  		US_DEBUGP("MS_RW_PATTERN\n");
> -		fw_name = "ene-ub6250/ms_rdwr.bin";
> +		fw_name = MS_RW_FIRMWARE;
>  		break;
>  	default:
>  		US_DEBUGP("----------- Unknown PATTERN ----------\n");

-Betty


--
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/