Linux SOC development
 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 1/3] soc/tegra: Cleanups for v6.14-rc1
Date: Fri, 10 Jan 2025 19:53:51 +0100	[thread overview]
Message-ID: <20250110185355.4143505-1-thierry.reding@gmail.com> (raw)

Hi ARM SoC maintainers,

The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.14-soc

for you to fetch changes up to 836b341cc8dab680acc06a7883bfeea89680b689:

  soc/tegra: fuse: Update Tegra234 nvmem keepout list (2025-01-10 18:51:46 +0100)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Cleanups for v6.14-rc1

This contains debugfs error handling cleanup, a typofix and an update to
the FUSE block's keepout list to properly allow reading these registers.

----------------------------------------------------------------
Kartik Rajput (1):
      soc/tegra: fuse: Update Tegra234 nvmem keepout list

Krzysztof Kozlowski (1):
      soc/tegra: cbb: Drop unnecessary debugfs error handling

liujing (1):
      soc/tegra: Fix spelling error in tegra234_lookup_slave_timeout()

 drivers/soc/tegra/cbb/tegra-cbb.c     | 20 ++++----------------
 drivers/soc/tegra/cbb/tegra234-cbb.c  |  2 +-
 drivers/soc/tegra/fuse/fuse-tegra30.c | 17 +++++++++++------
 3 files changed, 16 insertions(+), 23 deletions(-)

             reply	other threads:[~2025-01-10 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 18:53 Thierry Reding [this message]
2025-01-10 18:53 ` [GIT PULL 2/3] ARM: tegra: Device tree fixes for v6.14-rc1 Thierry Reding
2025-01-10 18:53 ` [GIT PULL 3/3] arm64: " 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=20250110185355.4143505-1-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