On Thu, Jun 12, 2014 at 05:23:16PM +0530, Sricharan R wrote:
> From: Nishanth Menon <nm@xxxxxx>
>
> remove un-necessary space in function pointer.
>
> Fixes checkpatch warning:
> WARNING: Unnecessary space before function pointer arguments
> #37: FILE: drivers/irqchip/irq-crossbar.c:37:
> + void (*write) (int, int);
>
> WARNING: Missing a blank line after declarations
> + int *register_offsets;
> + void (*write)(int, int);
>
> WARNING: Prefer kcalloc over kzalloc with multiply
> + cb->irq_map = kzalloc(max * sizeof(int), GFP_KERNEL);
>
> WARNING: Prefer kcalloc over kzalloc with multiply
> + cb->register_offsets = kzalloc(max * sizeof(int), GFP_KERNEL);
>
> Signed-off-by: Nishanth Menon <nm@xxxxxx>
> ---
> drivers/irqchip/irq-crossbar.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/irqchip/irq-crossbar.c b/drivers/irqchip/irq-crossbar.c
> index 5da9d36..58790d4 100644
> --- a/drivers/irqchip/irq-crossbar.c
> +++ b/drivers/irqchip/irq-crossbar.c
> @@ -34,7 +34,8 @@ struct crossbar_device {
> uint *irq_map;
> void __iomem *crossbar_base;
> int *register_offsets;
> - void (*write) (int, int);
> +
> + void (*write)(int, int);
The empty line here looks bogus to me. Did you re-run checkpatch after
fixing the unnecessary space to see if it still complained about having
a 'blank line after declarations'?
> };
>
> /**
> @@ -150,7 +151,7 @@ static int __init crossbar_of_init(struct device_node *node,
> goto err1;
>
> of_property_read_u32(node, "ti,max-irqs", &max);
> - cb->irq_map = kzalloc(max * sizeof(int), GFP_KERNEL);
> + cb->irq_map = kcalloc(max, sizeof(int), GFP_KERNEL);
> if (!cb->irq_map)
> goto err2;
>
> @@ -176,7 +177,7 @@ static int __init crossbar_of_init(struct device_node *node,
> }
> }
>
> - cb->register_offsets = kzalloc(max * sizeof(int), GFP_KERNEL);
> + cb->register_offsets = kcalloc(max, sizeof(int), GFP_KERNEL);
> if (!cb->register_offsets)
> goto err3;
I'm generally opposed to these sorts of checkpatch patches, especially
when they are just warnings. It's great for a new driver in the staging
tree, but it makes backporting future bugfixes that much harder when
drivers have been live in mainline.
If, in the future, you're changing code in this area, go ahead and
convert to kcalloc(), but I wouldn't do a separate patch for this kind
of thing.
Honestly, I would just drop this patch and not worry about it.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
