[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGRGNgUvEYG8fkruQCd-JxA5d=EjrK92A-mZ1rxUj39S5hdtbw@mail.gmail.com>
Date: Thu, 28 Jul 2016 22:02:29 +1000
From: Julian Calaby <julian.calaby@...il.com>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-wireless <linux-wireless@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Austin Shin <austin.shin@...el.com>,
Chris Park <chris.park@...el.com>,
Glen Lee <glen.lee@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Johnny Kim <johnny.kim@...el.com>, Leo Kim <leo.kim@...el.com>,
Tony Cho <tony.cho@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors <kernel-janitors@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: [PATCH 2/3] staging: wilc1000: One function call less in
mac_ioctl() after error detection
Hi Marcus,
On Mon, Jul 25, 2016 at 6:22 AM, SF Markus Elfring
<elfring@...rs.sourceforge.net> wrote:
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Sun, 24 Jul 2016 21:15:23 +0200
>
> The kfree() function was called in two cases by the mac_ioctl() function
> during error handling even if the passed variable did not contain a pointer
> for a valid data item.
>
> Improve this implementation detail by the introduction of another
> jump label.
>
> Signed-off-by: Markus Elfring <elfring@...rs.sourceforge.net>
This is pointless micro-optimisation: kfree(NULL) is perfectly valid
and buff is either malloc'd memory or NULL when it's called.
Thanks,
--
Julian Calaby
Email: julian.calaby@...il.com
Profile: http://www.google.com/profiles/julian.calaby/
Powered by blists - more mailing lists