public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: SongJingyi <u201912584@hust.edu.cn>
Cc: yangbo.lu@nxp.com, richardcochran@gmail.com, davem@davemloft.net,
	claudiu.manoil@nxp.com, hust-os-kernel-patches@googlegroups.com,
	error27@gmail.com, dzm91@hust.edu.cn, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptp_qoriq: fix memory leak in probe()
Date: Sat, 25 Mar 2023 02:20:18 +0000	[thread overview]
Message-ID: <167971081831.20950.12097733993259593696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230324031406.1895159-1-u201912584@hust.edu.cn>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 24 Mar 2023 11:14:06 +0800 you wrote:
> Smatch complains that:
> drivers/ptp/ptp_qoriq.c ptp_qoriq_probe()
> warn: 'base' from ioremap() not released.
> 
> Fix this by revising the parameter from 'ptp_qoriq->base' to 'base'.
> This is only a bug if ptp_qoriq_init() returns on the
> first -ENODEV error path.
> For other error paths ptp_qoriq->base and base are the same.
> And this change makes the code more readable.
> 
> [...]

Here is the summary with links:
  - ptp_qoriq: fix memory leak in probe()
    https://git.kernel.org/netdev/net/c/f33642224e38

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-03-25  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  3:14 [PATCH] ptp_qoriq: fix memory leak in probe() SongJingyi
2023-03-25  2:20 ` patchwork-bot+netdevbpf [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=167971081831.20950.12097733993259593696.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=dzm91@hust.edu.cn \
    --cc=error27@gmail.com \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=u201912584@hust.edu.cn \
    --cc=yangbo.lu@nxp.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