From: Markus Elfring <Markus.Elfring@web.de>
To: Ginger Li <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 14:21:08 +0200 [thread overview]
Message-ID: <1b56f03e-fab7-42a6-ac49-7b05a081639e@web.de> (raw)
In-Reply-To: <CAGp+u1Yw24hRsZfnD7sePs4C=xp-VLe1=OitaVRUrvE9tyNiiQ@mail.gmail.com>
>> 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
>
> I can update more information about the static analyzer (i.e., it is
> experimental and its reported log) in the patch.
> I believe this aligns with the known guidance,
Partly.
How many contributors would be involved in the mentioned software research so far?
> but I cannot provide
> the source code links.
Do you try to follow scientific development methods?
Will publishing requirements grow accordingly?
>>>>> 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.
Will opportunities be taken better into account for improved change descriptions?
Regards,
Markus
next prev parent reply other threads:[~2026-09-30 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 7:22 [PATCH] " 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 [this message]
2026-09-30 12:36 ` Ginger
2026-09-30 12:55 ` Markus Elfring
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=1b56f03e-fab7-42a6-ac49-7b05a081639e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®