[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140403090451.GE6991@mwanda>
Date: Thu, 3 Apr 2014 12:04:51 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Jimmy Li <coder.liss@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Teodora Baluta <teobaluta@...il.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>,
Michael Gunselmann <michael.gunselmann@...dium.uni-erlangen.de>,
Lisa Nguyen <lisa@...apiadmin.com>,
Martin Hofmann <martin.hofmann@...dium.uni-erlangen.de>,
Malcolm Priestley <tvboxspy@...il.com>,
Tülin İzer <tulinizer@...il.com>,
Archana kumari <archanakumari959@...il.com>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/staging/vt6655/iwctl.c fix a sparse warning
On Thu, Mar 27, 2014 at 08:28:44PM -0700, Jimmy Li wrote:
> You are right, I found that variable buf also don't make sense here,
> maybe this could be more clear.
>
> param = kzalloc(sizeof(struct viawget_wpa_param), GFP_KERNEL);
> if (param == NULL)
> return -ENOMEM;
>
> removing two unnecessary variable, buf and blen.
>
> In this situation, I should send a new patch v2 for it base on the
> previous path? or send a new patch include all changes?
We throw away the original patch and you send a v2. Use the subject:
[PATCH v2] drivers/staging/vt6655/iwctl.c fix a sparse warning
Under the Signed-off-by line put:
Signed-off-by: you
---
v2: additional cleanups as well.
regards,
dan carpenter
--
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/
Powered by blists - more mailing lists