Comment 4 for bug 1760099

@Breno in addition to the question above about which releases you're requesting, I have a new question about section mismatch warnings that the first patchset introduces:

WARNING: vmlinux.o(.text+0x22228): Section mismatch in reference from the function setup_rfi_flush() to the function .init.text:safe_stack_limit()
The function setup_rfi_flush() references
the function __init safe_stack_limit().
This is often because setup_rfi_flush lacks a __init
annotation or the annotation of safe_stack_limit is wrong.

WARNING: vmlinux.o(.text+0x22250): Section mismatch in reference from the function setup_rfi_flush() to the function .init.text:memblock_alloc_base()
The function setup_rfi_flush() references
the function __init memblock_alloc_base().
This is often because setup_rfi_flush lacks a __init
annotation or the annotation of memblock_alloc_base is wrong.

The "rfi-flush: Make it possible to call setup_rfi_flush() again" patch removes the __init__ annotation from setup_rfi_flush() and then the "rfi-flush: Call setup_rfi_flush() after LPM migration" patch makes it so that setup_rfi_flush() can be called outside of the initialization phase. If it is called outside of the initialization phase, it could call the two __init__ functions mentioned in the warnings above. So, from what I can tell, these are legitimate warnings. Are you all aware of these warnings and, if so, have you determined that they're not a problem?