mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, Sheetal <sheetal@nvidia.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	 Jon Hunter <jonathanh@nvidia.com>,
	Frank Li <Frank.Li@kernel.org>,
	 Thierry Reding <thierry.reding@kernel.org>,
	 Mohan Kumar <mkumard@nvidia.com>,
	Sameer Pujar <spujar@nvidia.com>,
	 linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] dmaengine: tegra210-adma: Add error logging on failure paths
Date: Mon, 08 Jun 2026 17:42:54 +0530	[thread overview]
Message-ID: <178092077429.96550.17091975503641429507.b4-ty@kernel.org> (raw)
In-Reply-To: <20260517163045.363444-1-sheetal@nvidia.com>


On Sun, 17 May 2026 16:30:45 +0000, Sheetal wrote:
> Add dev_err/dev_err_probe logging across failure paths to improve
> debuggability of DMA errors during runtime and probe.
> 
> Use return dev_err_probe() pattern where no cleanup is required in the
> probe function. On error paths that need explicit unwind, store the
> dev_err_probe() return value in ret before jumping to the cleanup label.
> Also convert existing dev_err calls in probe to dev_err_probe for
> consistency, and use dev_err in non-probe functions.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: tegra210-adma: Add error logging on failure paths
      commit: b55bfcc677dd58d808a53173e0574b466dc27b9f

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2026-06-08 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 16:30 Sheetal
2026-06-05 11:53 ` Jon Hunter
2026-06-08 12:12 ` Vinod Koul [this message]

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=178092077429.96550.17091975503641429507.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=sheetal@nvidia.com \
    --cc=spujar@nvidia.com \
    --cc=thierry.reding@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

all inboxes | Powered by JetHome®