From: Dan Carpenter <error27@gmail.com>
To: Ginger <ginger.jzllee@gmail.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [v3] dmaengine: tegra186-gpc-dma: Read channel state under the lock
Date: Thu, 1 Oct 2026 13:56:00 +0300 [thread overview]
Message-ID: <ar48QGIJ76kQmG--@stanley.mountain> (raw)
In-Reply-To: <CAGp+u1Yw24hRsZfnD7sePs4C=xp-VLe1=OitaVRUrvE9tyNiiQ@mail.gmail.com>
On Wed, Sep 30, 2026 at 01:57:11PM +0200, Ginger wrote:
> > >>> Were any more of your contributions supported by advanced source code analysis tools?
> > >
> > > If you meant AI tools, then at this stage, no. For this patch, I have
> > > used AI tools to help phrase
> > > the patch better, but I did not use them for code analysis.
> > Will this information trigger further collateral evolution?
> >
>
> The collateral evolution will only affect the experimental analyzer.
> It does not affect the submitted patch.
Please, don't use AI to write emails for you. Our inboxes are already
full enough.
staticthinking.wordpress.com/2026/01/27/no-ai-slop/
regards,
dan carpenter
prev parent reply other threads:[~2026-10-01 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 7:22 [PATCH] dmaengine: tegra186-gpc-dma: Read channel state under the lock Ginger Li
2026-09-23 19:44 ` Markus Elfring
2026-09-29 19:44 ` [PATCH v2] " Ginger Li
2026-09-30 7:04 ` Markus Elfring
2026-09-30 7:10 ` Ginger
2026-09-30 7:18 ` [v2] " Markus Elfring
2026-09-30 7:19 ` [PATCH v3] " Ginger Li
2026-09-30 7:25 ` Markus Elfring
2026-09-30 7:33 ` Ginger
2026-09-30 7:46 ` [v3] " Markus Elfring
2026-09-30 11:57 ` Ginger
2026-09-30 12:21 ` Markus Elfring
2026-09-30 12:36 ` Ginger
2026-09-30 12:55 ` Markus Elfring
2026-10-01 10:56 ` Dan Carpenter [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=ar48QGIJ76kQmG--@stanley.mountain \
--to=error27@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=dmaengine@vger.kernel.org \
--cc=ginger.jzllee@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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.