From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: "Verma, Devendra" <devverma@amd.com>,
sashiko-reviews@lists.linux.dev,
Devendra K Verma <devendra.verma@amd.com>,
Frank.Li@kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v5] dmaengine: dw-edma: Enable HDMA 64R/W Channels
Date: Wed, 1 Jul 2026 14:16:35 +0530 [thread overview]
Message-ID: <akTT639rZ712TZ5t@vaman> (raw)
In-Reply-To: <aj6iIr61LI9Sm10h@SMW015318>
On 26-06-26, 11:00, Frank Li wrote:
> On Fri, Jun 26, 2026 at 08:56:35PM +0530, Verma, Devendra wrote:
> > Hi Frank, Vinod
> >
> > Do you have any suggestion about handling of the repeated comments from
> > AI?
> > On every version of this patch the similar issues have been raised and
> > I am replying with the same answers as many version-times.
> > Please suggest so that multiple replies to the same queries by AI bot
> > can be managed.
>
> You can omit pre-existing. Only reply once when patch close to land. I hope
> there are tool, which can help identified comments and pull your previous
> reply.
Right, fixing preexisting is indeed optional but since it may impact your device,
we are looking forward to fixes on these from you. More important for us
is not adding new issues.
> On method may help:
>
> After I provided review-by, you can reply you already checked AI's results,
> so It help vnod offload his checking work.
Thanks this helps a lot.
> AI is quite new for us. we are looking for efficent flow to handle it.
Just like any other tool, it is tool which helps us. People should also
run the locally as well.
--
~Vinod
next prev parent reply other threads:[~2026-07-01 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 13:21 [PATCH v5] dmaengine: dw-edma: Enable HDMA 64R/W Channels Devendra K Verma
2026-06-26 13:46 ` sashiko-bot
2026-06-26 15:26 ` Verma, Devendra
2026-06-26 16:00 ` Frank Li
2026-07-01 8:46 ` Vinod Koul [this message]
2026-06-26 16:10 ` Frank Li
2026-06-29 5:57 ` Verma, Devendra
2026-06-30 19:58 ` Frank Li
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=akTT639rZ712TZ5t@vaman \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.li@oss.nxp.com \
--cc=devendra.verma@amd.com \
--cc=devverma@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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