From: patchwork-bot+linux-soc@kernel.org
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Fix possible memory leak OP-TEE driver for v6.1
Date: Mon, 21 Nov 2022 14:51:26 +0000 [thread overview]
Message-ID: <166904228601.4359.11968081106982724023.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y3d2OuJ60U30OkZe@jade>
Hello:
This pull request was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 18 Nov 2022 13:10:34 +0100 you wrote:
> Hello arm-soc maintainers,
>
> Please pull this small patch in the OP-TEE driver which fixes a possible
> memory leak in the error path of optee_register_device().
>
> Thanks,
> Jens
>
> [...]
Here is the summary with links:
- [GIT,PULL] Fix possible memory leak OP-TEE driver for v6.1
https://git.kernel.org/soc/soc/c/dc0e2470f4b9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-21 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 12:10 [GIT PULL] Fix possible memory leak OP-TEE driver for v6.1 Jens Wiklander
2022-11-21 14:51 ` patchwork-bot+linux-soc [this message]
2022-11-21 14:52 ` patchwork-bot+linux-soc
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=166904228601.4359.11968081106982724023.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=soc@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