From: Vinod Koul <vkoul@kernel.org>
To: Joy Zou <joy.zou@nxp.com>,
imx@lists.linux.dev, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 1/1] dmaengine: fsl-edma: correct max_segment_size setting
Date: Fri, 16 Feb 2024 18:04:51 +0530 [thread overview]
Message-ID: <170808689144.369567.8654351635732648675.b4-ty@kernel.org> (raw)
In-Reply-To: <20240207194733.2112870-1-Frank.Li@nxp.com>
On Wed, 07 Feb 2024 14:47:32 -0500, Frank Li wrote:
> Correcting the previous setting of 0x3fff to the actual value of 0x7fff.
>
> Introduced new macro 'EDMA_TCD_ITER_MASK' for improved code clarity and
> utilization of FIELD_GET to obtain the accurate maximum value.
>
>
Applied, thanks!
[1/1] dmaengine: fsl-edma: correct max_segment_size setting
commit: a79f949a5ce1d45329d63742c2a995f2b47f9852
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-02-16 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 19:47 [PATCH 1/1] dmaengine: fsl-edma: correct max_segment_size setting Frank Li
2024-02-16 12:34 ` 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=170808689144.369567.8654351635732648675.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=linux-kernel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).