Re: [Crash-utility] [PATCH 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64

On 10/14/22 20:10, Conor Dooley wrote: > Without whitespace highlighting, your change threw me for a sec.. But > yeah, having the overline is inconsistent with other headings in the > doc. > > What I wanted to ask about was the linelength as I don't know anything > about rst. Is it possible to avoid having the ~150 character line or is > that a necessary evil? > I think the section describes correct range exports; however since there are many such ranges with distinct purposes, it is better to split the section into multiple sections describing each range. If we go without splitting, the 150-character header is necessary (I don't know how to split the header text line without trigger any warnings).

Thanks.