[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGTfZH09FiaAzEy56DYu0JY2CHwfB3+m6kP6Xog1Zctxs_m7zg@mail.gmail.com>
Date: Fri, 25 Apr 2014 00:06:18 +0900
From: Chanwoo Choi <cwchoi00@...il.com>
To: Felipe Balbi <balbi@...com>
Cc: Chanwoo Choi <cw00.choi@...sung.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"myungjoo.ham@...sung.com" <myungjoo.ham@...sung.com>,
gg@...mlogic.co.uk, Kishon Vijay Abraham I <kishon@...com>,
ckeepax@...nsource.wolfsonmicro.com,
Mark Brown <broonie@...nel.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCHv3 1/9] extcon: Add extcon_dev_allocate/free() to control
the memory of extcon device
On Fri, Apr 25, 2014 at 12:03 AM, Felipe Balbi <balbi@...com> wrote:
> Hi,
>
> On Thu, Apr 24, 2014 at 11:58:29PM +0900, Chanwoo Choi wrote:
>> >> +void extcon_dev_free(struct extcon_dev *edev)
>> >> +{
>> >> + if (edev)
>> >> + kfree(edev);
>> >
>> > kfree(NULL) is safe
>>
>> I don't understand about meaning 'kfree(NULL)'.
>> Why do I free 'NULL' pointer' instead of 'edev' pointer?
>
> you don't need to check if evdev is valid before calling kfree() on it
> because if it happens to be NULL, no cute bunnies will be sacrificed.
>
OK, I'll fix it as following code without checking whether 'edev' is
NULL or not.
void extcon_dev_free(struct extcon_dev *edev)
{
kfree(edev);
}
Thanks,
Chanwoo Choi
--
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