public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Ketan Patil <ketanp@nvidia.com>,
	krzk@kernel.org, thierry.reding@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v7 0/6] memory: tegra: Add MC error logging support for Tegra264 SoC
Date: Fri, 6 Mar 2026 10:22:11 +0000	[thread overview]
Message-ID: <18c339ea-d535-43a6-96d1-e583dc05ba87@nvidia.com> (raw)
In-Reply-To: <20260226163115.1152181-1-ketanp@nvidia.com>


On 26/02/2026 16:31, Ketan Patil wrote:
> In Tegra264, different components from memory subsystems like Memory
> Controller Fabric (MCF), HUB, HUB Common (HUBC), Side Band Shim (SBS)
> and MC Channels have different interrupt lines for receiving memory
> controller error interrupts. This patch set includes changes to add
> support and enable Memory Controller error logging for Tegra264.
> 
> Ketan Patil (6):
>    memory: tegra: Group error handling related registers
>    memory: tegra: Group register and fields
>    memory: tegra: Add support for multiple IRQs
>    memory: tegra: Group SoC specific fields
>    memory: tegra: Prepare for supporting multiple intmask registers
>    memory: tegra: Add MC error logging support for Tegra264
> 

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>

Krzysztof, let us know if you are OK with this version? If so, would be 
great to get this into -next.

Thanks!
Jon

-- 
nvpublic


  parent reply	other threads:[~2026-03-06 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 16:31 [PATCH v7 0/6] memory: tegra: Add MC error logging support for Tegra264 SoC Ketan Patil
2026-02-26 16:31 ` [PATCH v7 1/6] memory: tegra: Group error handling related registers Ketan Patil
2026-02-26 16:31 ` [PATCH v7 2/6] memory: tegra: Group register and fields Ketan Patil
2026-02-26 16:31 ` [PATCH v7 3/6] memory: tegra: Add support for multiple IRQs Ketan Patil
2026-02-26 16:31 ` [PATCH v7 4/6] memory: tegra: Group SoC specific fields Ketan Patil
2026-02-26 16:31 ` [PATCH v7 5/6] memory: tegra: Prepare for supporting multiple intmask registers Ketan Patil
2026-02-26 16:31 ` [PATCH v7 6/6] memory: tegra: Add MC error logging support for Tegra264 Ketan Patil
2026-03-06 10:22 ` Jon Hunter [this message]
2026-03-07 17:00 ` [PATCH v7 0/6] memory: tegra: Add MC error logging support for Tegra264 SoC Krzysztof Kozlowski
2026-03-09 14:16   ` Ketan Patil
2026-03-07 17:02 ` Krzysztof Kozlowski

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=18c339ea-d535-43a6-96d1-e583dc05ba87@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=ketanp@nvidia.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.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