On Thu, Nov 14, 2024 at 10:47:23AM +0100, Ingo Molnar wrote:
> I think in-line documentation is better in this case: the primary defense
> against mistakes and misunderstandings is in the source code itself.
>
> And "it's too long" is an argument *against* moving it out into some obscure
> place 99% of developers aren't even aware of...
You mean developers can't even read?
/*
* See Documentation/arch/x86/ for details on this mitigation
* implementation.
*/
And if we want to expand the "why" and do proper documentation on the
implementation decisions of each mitigation, we still keep it there in the
code?
Or we do one part in Documentation/ and another part in the code?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
