public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: <vkoul@kernel.org>
Cc: Mohan Kumar D <mkumard@nvidia.com>, <thierry.reding@gmail.com>,
	<jonathanh@nvidia.com>, <dmaengine@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] Tegra ADMA fixes
Date: Sat, 1 Feb 2025 17:14:41 -0800	[thread overview]
Message-ID: <20250201171441.407b91cb@kernel.org> (raw)
In-Reply-To: <20250116162033.3922252-1-mkumard@nvidia.com>

On Thu, 16 Jan 2025 21:50:31 +0530 Mohan Kumar D wrote:
> - Fix build error due to 64-by-32 division
> - Additional check for adma max page

Hi!

What's happening with this series? The buggy commit reached Linus's
tree and broke 32b builds for everybody. The patches look 2 weeks old.

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 16:20 [PATCH v3 0/2] Tegra ADMA fixes Mohan Kumar D
2025-01-16 16:20 ` [PATCH v3 1/2] dmaengine: tegra210-adma: Fix build error due to 64-by-32 division Mohan Kumar D
2025-01-17 14:52   ` Jon Hunter
2025-02-04 15:36   ` Thierry Reding
2025-02-04 16:43     ` Mohan Kumar D
2025-02-04 17:03       ` Thierry Reding
2025-02-04 17:18         ` Jon Hunter
2025-02-04 17:58           ` Thierry Reding
2025-02-05  3:31             ` Mohan Kumar D
2025-01-16 16:20 ` [PATCH v3 2/2] dmaengine: tegra210-adma: check for adma max page Mohan Kumar D
2025-01-17 14:54   ` Jon Hunter
2025-02-02  1:14 ` Jakub Kicinski [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=20250201171441.407b91cb@kernel.org \
    --to=kuba@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox