From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-mips@vger.kernel.org, dengcheng.zhu@imgtec.com,
Steven.Hill@imgtec.com, Qais.Yousef@imgtec.com,
blogic@openwrt.org
Subject: Re: [PATCH v2 0/2] MIPS: fix possible memory leak while module exiting
Date: Tue, 22 Nov 2022 13:29:53 +0100 [thread overview]
Message-ID: <20221122122953.GA11276@alpha.franken.de> (raw)
In-Reply-To: <20221104033945.1120044-1-yangyingliang@huawei.com>
On Fri, Nov 04, 2022 at 11:39:43AM +0800, Yang Yingliang wrote:
> This patchset fixes two device name leaks while module exiting
> in normal or error path.
>
> v1 -> v2:
> Add fix tag in patch #1.
>
> Yang Yingliang (2):
> MIPS: vpe-mt: fix possible memory leak while module exiting
> MIPS: vpe-cmp: fix possible memory leak while module exiting
>
> arch/mips/kernel/vpe-cmp.c | 4 ++--
> arch/mips/kernel/vpe-mt.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.25.1
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-11-22 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 3:39 [PATCH v2 0/2] MIPS: fix possible memory leak while module exiting Yang Yingliang
2022-11-04 3:39 ` [PATCH v2 1/2] MIPS: vpe-mt: " Yang Yingliang
2022-11-22 11:21 ` Thomas Bogendoerfer
2022-11-22 11:41 ` Yang Yingliang
2022-11-22 12:07 ` Thomas Bogendoerfer
2022-11-04 3:39 ` [PATCH v2 2/2] MIPS: vpe-cmp: " Yang Yingliang
2022-11-22 12:29 ` Thomas Bogendoerfer [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=20221122122953.GA11276@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Qais.Yousef@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=blogic@openwrt.org \
--cc=dengcheng.zhu@imgtec.com \
--cc=linux-mips@vger.kernel.org \
--cc=yangyingliang@huawei.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).