Re: [v3] dmaengine: tegra186-gpc-dma: Read channel state under the lock

[Markus Elfring]

>> How many contributors would be involved in the mentioned software research so far?
> 
> Currently, I am the only one contributing to the source code of the
> analyzer. My co-workers
> provide research-oriented discussions but not bug reviews/implementation.

Thus it seems that there is a corresponding research group somewhere.


> Regarding this, how would it be reflected in the patch?

See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.3-rc5#n545


>> Do you try to follow scientific development methods?
>>
>> Will publishing requirements grow accordingly?
>>
> Yes. The source code will be made public once the research work gets published.

Would there any research grants be involved as another related information source?


>>>> 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?
>>
> 
> May I kindly ask what opportunities you are referring to?

I indicated also a possibility to avoid another typo (for example).


>                                                           If you meant
> that whether
> future reports generated potentially with the help of AI tools will
> credit AI tools, then
> yes.
* Adjustments for word wrapping

* Additional tags

* How will locking analyses evolve further?


Regards,
Markus