linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: sean.wang@mediatek.com, lorenzo.bianconi@redhat.com
Cc: linux-mediatek@lists.infradead.org, ryder.lee@mediatek.com,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mt76: mt7663u: fix memory leak in set key
Date: Thu, 9 Jul 2020 12:15:44 +0200	[thread overview]
Message-ID: <943c2cd1-71a4-8ddc-f7a9-83e6350db0fd@nbd.name> (raw)
In-Reply-To: <57b81f8efe7e767616a0d5957728756cbfdfa235.1594148548.git.sean.wang@mediatek.com>

On 2020-07-07 21:16, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
> 
> Fix memory leak in set key.
> 
> v1 -> v2:
> 	- remove unneeded kfree
> 
> Fixes: eb99cc95c3b6 ("mt76: mt7615: introduce mt7663u support")
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Next time, please move the changelog below the '---' line so that it
doesn't end up in the patch description.
I will fix it up locally in my tree.

Thanks,

- Felix

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      parent reply	other threads:[~2020-07-09 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 19:16 [PATCH v2 1/3] mt76: mt7663u: fix memory leak in set key sean.wang
2020-07-07 19:16 ` [PATCH v2 2/3] mt76: mt7663u: fix potential memory leak in mcu message handler sean.wang
2020-07-07 19:16 ` [PATCH v2 3/3] mt76: mt7615: " sean.wang
2020-07-07 21:18 ` [PATCH v2 1/3] mt76: mt7663u: fix memory leak in set key Lorenzo Bianconi
2020-07-09 10:15 ` Felix Fietkau [this message]

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=943c2cd1-71a4-8ddc-f7a9-83e6350db0fd@nbd.name \
    --to=nbd@nbd.name \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=ryder.lee@mediatek.com \
    --cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).