[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cda77a7f-470d-21eb-f5ec-dac004b32bc5@linux.alibaba.com>
Date: Fri, 14 Oct 2022 21:44:09 +0800
From: Xianting Tian <xianting.tian@...ux.alibaba.com>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Conor Dooley <conor@...nel.org>
Cc: paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, anup@...infault.org, heiko@...ech.de,
guoren@...nel.org, mick@....forth.gr,
alexandre.ghiti@...onical.com, bhe@...hat.com, vgoyal@...hat.com,
dyoung@...hat.com, corbet@....net, Conor.Dooley@...rochip.com,
kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
crash-utility@...hat.com, heinrich.schuchardt@...onical.com,
k-hagio-ab@....com, hschauhan@...ltrace.org, yixun.lan@...il.com
Subject: Re: [PATCH 2/2] Documentation: kdump: describe VMCOREINFO export for
RISCV64
在 2022/10/14 下午9:23, Bagas Sanjaya 写道:
> 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, I send V2 patch, please help review.
https://lkml.org/lkml/2022/10/14/447
>
> Thanks.
>
Powered by blists - more mailing lists