From: David Miller <davem@davemloft.net>
To: liujian56@huawei.com
Cc: madalin.bucur@nxp.com, kuba@kernel.org, laurentiu.tudor@nxp.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] dpaa_eth: Fix one possible memleak in dpaa_eth_probe
Date: Fri, 17 Jul 2020 18:41:45 -0700 (PDT) [thread overview]
Message-ID: <20200717.184145.1710848863414831357.davem@davemloft.net> (raw)
In-Reply-To: <20200717090528.19683-1-liujian56@huawei.com>
From: Liu Jian <liujian56@huawei.com>
Date: Fri, 17 Jul 2020 17:05:28 +0800
> When dma_coerce_mask_and_coherent() fails, the alloced netdev need to be freed.
>
> Fixes: 060ad66f9795 ("dpaa_eth: change DMA device")
> Signed-off-by: Liu Jian <liujian56@huawei.com>
This is a bug fix introduced in v5.5, therefore it should be targetting
'net' instead of 'net-next'.
next prev parent reply other threads:[~2020-07-18 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:05 [PATCH net-next] dpaa_eth: Fix one possible memleak in dpaa_eth_probe Liu Jian
2020-07-18 1:41 ` David Miller [this message]
2020-07-20 13:44 ` liujian (CE)
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=20200717.184145.1710848863414831357.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=laurentiu.tudor@nxp.com \
--cc=liujian56@huawei.com \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
/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).