All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Mohan Kumar D <mkumard@nvidia.com>,
	vkoul@kernel.org, thierry.reding@gmail.com
Cc: dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Tegra ADMA fixes
Date: Wed, 5 Feb 2025 14:03:37 +0000	[thread overview]
Message-ID: <d644a35e-7dfd-4eb0-a7c3-8dae96e09657@nvidia.com> (raw)
In-Reply-To: <20250205033131.3920801-1-mkumard@nvidia.com>


On 05/02/2025 03:31, Mohan Kumar D wrote:
> - Fix build error due to 64-by-32 division
> - Additional check for adma max page
> 
> Mohan Kumar D (2):
>    dmaengine: tegra210-adma: Fix build error due to 64-by-32 division
>    dmaengine: tegra210-adma: check for adma max page
> 
>   drivers/dma/tegra210-adma.c | 20 ++++++++++++++++----
>   1 file changed, 16 insertions(+), 4 deletions(-)
> 


Thanks! For the series ...

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

Cheers
Jon

-- 
nvpublic


      parent reply	other threads:[~2025-02-05 14:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  3:31 [PATCH v4 0/2] Tegra ADMA fixes Mohan Kumar D
2025-02-05  3:31 ` [PATCH v4 1/2] dmaengine: tegra210-adma: Fix build error due to 64-by-32 division Mohan Kumar D
2025-02-05 11:27   ` Jon Hunter
2025-02-05 11:28     ` Jon Hunter
2025-02-05 13:25   ` Thierry Reding
2025-02-10 11:02   ` Vinod Koul
2025-02-10 11:15     ` Mohan Kumar D
2025-02-10 11:23       ` Vinod Koul
2025-02-05  3:31 ` [PATCH v4 2/2] dmaengine: tegra210-adma: check for adma max page Mohan Kumar D
2025-02-05 11:40   ` Jon Hunter
2025-02-05 12:58     ` Mohan Kumar D
2025-02-05 13:24       ` Thierry Reding
2025-02-05 13:25   ` Thierry Reding
2025-02-05 14:03 ` Jon Hunter [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=d644a35e-7dfd-4eb0-a7c3-8dae96e09657@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.