From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/5] firmware: tegra: Changes for v6.9-rc1
Date: Fri, 23 Feb 2024 18:48:45 +0100 [thread overview]
Message-ID: <20240223174849.1509465-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20240223174849.1509465-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.9-firmware
for you to fetch changes up to 1315848f1f8a0100cb6f8a7187bc320c5d98947f:
firmware: tegra: bpmp: Return directly after a failed kzalloc() in get_filename() (2024-02-21 17:10:32 +0100)
Thanks,
Thierry
----------------------------------------------------------------
firmware: tegra: Changes for v6.9-rc1
Contains a fix that makes sure we don't unnecessarily call kfree().
----------------------------------------------------------------
Markus Elfring (1):
firmware: tegra: bpmp: Return directly after a failed kzalloc() in get_filename()
drivers/firmware/tegra/bpmp-debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next prev parent reply other threads:[~2024-02-23 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 17:48 [GIT PULL 1/5] soc/tegra: Changes for v6.9-rc1 Thierry Reding
2024-02-23 17:48 ` Thierry Reding [this message]
2024-02-23 17:48 ` [GIT PULL 3/5] dt-bindings: " Thierry Reding
2024-02-23 17:48 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2024-02-23 17:48 ` [GIT PULL 5/5] arm64: " Thierry Reding
2024-02-29 17:02 ` [GIT PULL 1/5] soc/tegra: Changes " patchwork-bot+linux-soc
2024-03-04 16:12 ` 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=20240223174849.1509465-2-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.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