On Thu, Jun 09, 2011 at 04:14:34PM +0300, Kalle Valo wrote:
> Dan Carpenter <error27@xxxxxxxxx> writes:
>
> >> --- a/drivers/staging/ath6kl/os/linux/ar6000_drv.c
> >> +++ b/drivers/staging/ath6kl/os/linux/ar6000_drv.c
> >> @@ -954,9 +954,13 @@ ar6000_transfer_bin_file(struct ar6_softc *ar, AR6K_BIN_FILE file, u32 address,
> >> const char *filename;
> >> const struct firmware *fw_entry;
> >> u32 fw_entry_size;
> >> + u8 **buf;
> >> + size_t *buf_len;
> >
> > Don't make buf_len a pointer that just makes the code messier.
>
> I need the pointer later so that I can store the length:
>
> *buf_len = fw_entry->size;
No. The normal way to store an int is to do it like this:
buf_len = fw_entry->size;
[snip]
> >> + if (*buf == NULL) {
> >> + if ((A_REQUEST_FIRMWARE(&fw_entry, filename, ((struct device *)ar->osDevInfo.pOSDevice))) != 0)
> >> + {
> > ^
> >
> > This is on the wrong line.
>
> I'll answer this and all the other style comments in one go:
>
> All the style issues are from the original code. I want to separate
> functional and cleanup patches so I didn't do any cleanup in this
> patch. But as we are doing the cleanup in a different tree anyway I
> didn't see the point of sending a separate cleanup patch.
>
No. That was in a section of code which was added. There wasn't
a "buf" variable in the original code. You obviously know how it's
supposed to look because you did it correctly on the line before.
What I'm saying is don't be lazy and careless. That's not a
difficult thing.
regards,
dan carpenter
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
