From: Vinod Koul <vkoul@kernel.org>
To: Mohan Kumar D <mkumard@nvidia.com>
Cc: 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,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v4 1/2] dmaengine: tegra210-adma: Fix build error due to 64-by-32 division
Date: Mon, 10 Feb 2025 16:53:34 +0530 [thread overview]
Message-ID: <Z6nhtrs1rYXcQOBl@vaman> (raw)
In-Reply-To: <2d190825-5284-4ac6-9735-051849bc9bb6@nvidia.com>
On 10-02-25, 16:45, Mohan Kumar D wrote:
>
> On 10-02-2025 16:32, Vinod Koul wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > Hi Mohan,
> >
> > On 05-02-25, 09:01, Mohan Kumar D wrote:
> > > Kernel test robot reported the build errors on 32-bit platforms due to
> > > plain 64-by-32 division. Following build erros were reported.
> > Patch should describe the change! Please revise subject to describe that
> > and not fix build error... This can come in changelog and below para is
> > apt
> Sure, Will update the subject and resend the updated patch
Please collect the acks as well
--
~Vinod
next prev parent reply other threads:[~2025-02-10 11:23 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 [this message]
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 ` [PATCH v4 0/2] Tegra ADMA fixes Jon Hunter
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=Z6nhtrs1rYXcQOBl@vaman \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mkumard@nvidia.com \
--cc=stable@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