From: James Clark <james.clark@arm.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: mike.leach@linaro.org, leo.yan@linaro.org,
linux-kernel@vger.kernel.org, german.gomez@arm.com,
Jonathan Corbet <corbet@lwn.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
suzuki.poulose@arm.com, coresight@lists.linaro.org,
mathieu.poirier@linaro.org
Subject: Re: [PATCH v3 2/2] coresight: etm4x: docs: Add documentation for 'ts_source' sysfs interface
Date: Wed, 24 Aug 2022 14:59:14 +0100 [thread overview]
Message-ID: <d79df47e-e7b2-8492-7425-bd6030679b57@arm.com> (raw)
In-Reply-To: <fc054b1c-b3c8-f627-d4c1-d916a2d286ca@gmail.com>
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
next prev parent reply other threads:[~2022-08-24 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 16:06 [PATCH v3 0/2] coresight: etm4x: Expose default timestamp source in sysfs James Clark
2022-08-23 16:06 ` [PATCH v3 1/2] " James Clark
2022-08-23 16:06 ` [PATCH v3 2/2] coresight: etm4x: docs: Add documentation for 'ts_source' sysfs interface James Clark
2022-08-24 2:54 ` Bagas Sanjaya
2022-08-24 13:59 ` James Clark [this message]
2022-08-26 19:55 ` [PATCH v3 0/2] coresight: etm4x: Expose default timestamp source in sysfs Mathieu Poirier
2022-08-30 17:29 ` James Clark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d79df47e-e7b2-8492-7425-bd6030679b57@arm.com \
--to=james.clark@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=german.gomez@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox