Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753572AbbHRRHB (ORCPT ); Tue, 18 Aug 2015 13:07:01 -0400 Received: from mail-yk0-f173.google.com ([209.85.160.173]:36491 "EHLO mail-yk0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750871AbbHRRG7 convert rfc822-to-8bit (ORCPT ); Tue, 18 Aug 2015 13:06:59 -0400 MIME-Version: 1.0 In-Reply-To: <20150818091530.GH5610@mwanda> References: <55D238D4.20800@broadcom.com> <20150817234628.GK5558@mwanda> <20150818091530.GH5610@mwanda> From: =?UTF-8?Q?Rapha=C3=ABl_Beamonte?= Date: Tue, 18 Aug 2015 13:06:39 -0400 X-Google-Sender-Auth: PJ2P3IUWuVlDg9YmJEw66rFRZpQ Message-ID: Subject: Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak To: Dan Carpenter Cc: Greg Kroah-Hartman , Rachel Kim , Dean Lee , Chris Park , devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org, Johnny Kim , linux-kernel@vger.kernel.org, Arend van Spriel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 23 2015-08-18 5:15 GMT-04:00 Dan Carpenter : > To be honest, I have lost track of this patchset. If you are planning > to redo the other patches can you send it in a new thread? Actually, Greg already included the "return statement" and "DECLARE_WILC_BUFFER" ones. The replacement of printk by netdev_* needs more work on my side to get the net_device to be able to use the netdev_* functions. And apparently Greg already received another patch with the "FREE_WILC_BUFFER" replacement, though I don't see it in the staging-testing tree yet. So, I think this patch is the last one of this patchset that has to be treated! That's why I rebased it on top of the current staging-testing tree on my last send. Thanks, Raphaël -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/