Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Rameshwar Sahu <sahu.rameshwar73@gmail.com>
Subject: Re: [PATCH] [wl18xx] Fix memory leakage if kzalloc fails
Date: Fri, 07 Oct 2016 07:50:46 +0300	[thread overview]
Message-ID: <87oa2w2255.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CAFqt6zYpMJKrX51--eHXKSEcgb+KVJ7ULjoL==DNKyOeOB5_4Q@mail.gmail.com> (Souptick Joarder's message of "Fri, 7 Oct 2016 00:21:13 +0530")

Souptick Joarder <jrdr.linux@gmail.com> writes:

> Hi Julian,
>
>
> On Thu, Oct 6, 2016 at 3:05 PM, Julian Calaby <julian.calaby@gmail.com> wrote:
>> Hi,
>>
>> On Wed, Oct 5, 2016 at 10:50 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>>> This patch is added to properly handle memory leak if kzalloc fails
>>> in wl18xx_scan_send() and wl18xx_scan_sched_scan_config()
>>
>> What memory leak?
>
> My Apologies here. I was addressing here about freeing the invalid memories.
> But I put wrong description. I will resend this patch with proper
> descriptions and addressing your comments.

Also the prefix in the title should be "wl18xx: ", not "[wl18xx]". See:

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#subject_name

-- 
Kalle Valo

  reply	other threads:[~2016-10-07  4:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 11:50 [PATCH] [wl18xx] Fix memory leakage if kzalloc fails Souptick Joarder
2016-10-06  9:35 ` Julian Calaby
2016-10-06 18:51   ` Souptick Joarder
2016-10-07  4:50     ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-05 13:09 Souptick Joarder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa2w2255.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=jrdr.linux@gmail.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sahu.rameshwar73@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox