From: Markus Elfring <Markus.Elfring@web.de>
To: Ginger <ginger.jzllee@gmail.com>,
dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org
Cc: 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: Wed, 30 Sep 2026 09:46:25 +0200 [thread overview]
Message-ID: <cb64813e-0a11-4c14-9bea-45f8dceff115@web.de> (raw)
In-Reply-To: <CAGp+u1aTQvE_o=nObMb0LvuwmdFukG9qBeKGDvwcf5-ckG9xyg@mail.gmail.com>
>> Under which circumstances will additional background information become available?
>
> The static analyzer is a research-based one, built upon the LLVM IR.
> The analysis is founded
> on a symbolic model (not an ML model) for concurrency bugs.
Thanks for such a hint.
> And due to
> the anonymity
> requirements, I am afraid I cannot reveal further information.
How does this feedback fit to other known guidance?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/researcher-guidelines.rst?h=v7.3-rc5#n5
>>> 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?
Regards,
Markus
next prev parent reply other threads:[~2026-09-30 7:46 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 ` Markus Elfring [this message]
2026-09-30 11:57 ` [v3] " 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
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=cb64813e-0a11-4c14-9bea-45f8dceff115@web.de \
--to=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.