linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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/7] firmware: tegra: Changes for v5.20-rc1
Date: Fri,  8 Jul 2022 20:56:03 +0200	[thread overview]
Message-ID: <20220708185608.676474-3-thierry.reding@gmail.com> (raw)
In-Reply-To: <20220708185608.676474-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.20-firmware

for you to fetch changes up to afcdb8e55c91c6ff0700ab272fd0f74e899ab884:

  firmware: tegra: Fix error check return value of debugfs_create_file() (2022-07-08 17:56:03 +0200)

Thanks,
Thierry

----------------------------------------------------------------
firmware: tegra: Changes for v5.20-rc1

Contains a fix that avoids unaligned accesses to IPC memory, which in
turn helps in suppressing speculative reads from out-of-bounds memory.

Another patch performs some minor cleanup around debugfs API usage.

----------------------------------------------------------------
Lv Ruyi (1):
      firmware: tegra: Fix error check return value of debugfs_create_file()

Timo Alho (1):
      firmware: tegra: bpmp: Do only aligned access to IPC memory area

 drivers/firmware/tegra/bpmp-debugfs.c | 10 +++++-----
 drivers/firmware/tegra/bpmp.c         |  6 +++---
 2 files changed, 8 insertions(+), 8 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-07-08 18:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 18:56 [GIT PULL 0/7] NVIDIA Tegra changes for v5.20-rc1 Thierry Reding
2022-07-08 18:56 ` [GIT PULL 1/7] soc/tegra: Changes " Thierry Reding
2022-07-12 13:27   ` Arnd Bergmann
2022-07-13 10:58     ` Thierry Reding
2022-07-13 12:14       ` Arnd Bergmann
2022-07-13 12:19         ` Jon Hunter
2022-07-13 12:36           ` Arnd Bergmann
2022-07-14  6:49             ` Jon Hunter
2022-07-13 20:22         ` Thierry Reding
2022-07-14  6:30           ` Jon Hunter
2022-07-14 14:45           ` Arnd Bergmann
2022-07-14 13:31         ` Borislav Petkov
2022-07-15  8:06           ` Sumit Gupta
2022-07-28 17:34             ` Thierry Reding
2022-08-22  9:31               ` Sumit Gupta
2022-09-27 16:00           ` Thierry Reding
2022-07-08 18:56 ` Thierry Reding [this message]
2022-07-08 18:56 ` [GIT PULL 3/7] dt-bindings: " Thierry Reding
2022-07-08 18:56 ` [GIT PULL 4/7] memory: tegra: " Thierry Reding
2022-07-08 18:56 ` [GIT PULL 5/7] ARM: tegra: Device tree changes " Thierry Reding
2022-07-08 18:56 ` [GIT PULL 6/7] arm64: " Thierry Reding
2022-07-08 18:56 ` [GIT PULL 7/7] arm64: tegra: Default configuration updates " Thierry Reding

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=20220708185608.676474-3-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;
as well as URLs for NNTP newsgroup(s).