[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d79df47e-e7b2-8492-7425-bd6030679b57@arm.com>
Date: Wed, 24 Aug 2022 14:59:14 +0100
From: James Clark <james.clark@....com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: mike.leach@...aro.org, leo.yan@...aro.org,
linux-kernel@...r.kernel.org, german.gomez@....com,
Jonathan Corbet <corbet@....net>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
suzuki.poulose@....com, coresight@...ts.linaro.org,
mathieu.poirier@...aro.org
Subject: Re: [PATCH v3 2/2] coresight: etm4x: docs: Add documentation for
'ts_source' sysfs interface
On 24/08/2022 03:54, Bagas Sanjaya wrote:
> On 8/23/22 23:06, James Clark wrote:
>> +:Example:
>> + ``$> cat ts_source``
>> +
>> + ``$> 1``
>> +
>
> Shouldn't literal code block be used instead for example snippet
> above?
>
It's consistent with the rest of the file. I think consistency for
something like this is more important than accuracy otherwise the new
entry would appear out of place.
Maybe they should all be changed to a different style, but that would be
a separate change unrelated to this set.
James
Powered by blists - more mailing lists