Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] doc: rST title underline too short for vmware_record_panic_msg --
commit c541f42ddd949c322e4b6facb84fc17737ed184a Author: Zack Rusin <[email protected]> x86/vmware: Add the vmware_record_panic_msg sysctl This commit adds a new sysctl kernel.vmware_record_panic_msg to control whether panic or fatal-oops data is written to the host log before kdump. It allows administrators to configure this logging behavior depending on guest encryption, and defers sysctl registration until the logger is ready. Link: https://lore.kernel.org/r/4e73yd2ofpdzl6rptzvd74no3hnyfblknoq7wzxlw7f3zjbz7c@srfabx6lsusj > diff --git a/Documentation/admin-guide/sysctl/kernel.rst > b/Documentation/admin-guide/sysctl/kernel.rst > index ffea61d448ebb..be13c143b8bb0 100644 > --- a/Documentation/admin-guide/sysctl/kernel.rst > +++ b/Documentation/admin-guide/sysctl/kernel.rst [ ... ] > @@ -1690,6 +1690,26 @@ entry will default to 2 instead of 0. > = ============================================================= > > > +vmware_record_panic_msg > +====================== [Severity: Low] Is the underline for this section title one character too short? The title vmware_record_panic_msg is 23 characters long, but the underline is only 22 characters long. In reStructuredText, the underline must be at least as long as the text it underlines, so this regression will trigger a warning during Sphinx documentation builds. > + > +Controls whether panic or fatal-oops kmsg data is written to the host's > +``vmware.log`` before kdump. This setting does not control the separate -- Sashiko AI review ยท https://sashiko.dev/#/patchset/[email protected]?part=5
