From: Akira Yokosawa <akiyks@gmail.com>
To: vilhelm.gray@gmail.com
Cc: jic23@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v15 07/13] docs: counter: Document character device interface
Date: Sun, 22 Aug 2021 11:03:38 +0900 [thread overview]
Message-ID: <f6930072-c487-a102-931c-53a79515d5fa@gmail.com> (raw)
In-Reply-To: <YSDa667n6pi4O8iT@shinobu>
(dropped most CCs)
Hello William,
I spotted a minor error while browsing documentation updates.
On Sat, 21 Aug 2021 19:52:27 +0900, William Breathitt Gray wrote:
> On Sun, Aug 15, 2021 at 05:51:02PM +0100, Jonathan Cameron wrote:
>> On Mon, 9 Aug 2021 21:37:32 +0900
>> William Breathitt Gray <vilhelm.gray@gmail.com> wrote:
...
>> > +
>> > +Counter events can be configured by users to report various Counter
>> > +data of interest. This can be conceptualized as a list of Counter
>> > +component read calls to perform. For example:
>> > +
>> > + +-------------------------------------------------+
This needs to be:
+------------------------+------------------------+
, so that the table structure can be properly recognized by Sphinx
(kernel-doc tool).
Thanks, Akira
>> > + | COUNTER_EVENT_OVERFLOW | COUNTER_EVENT_INDEX |
>> > + +========================+========================+
>> > + | Channel 0 | Channel 0 |
>> > + +------------------------+------------------------+
>> > + | * Count 0 | * Signal 0 |
>> > + | * Count 1 | * Signal 0 Extension 0 |
>> > + | * Signal 3 | * Extension 4 |
>> > + | * Count 4 Extension 2 +------------------------+
>> > + | * Signal 5 Extension 0 | Channel 1 |
>> > + | +------------------------+
>> > + | | * Signal 4 |
>> > + | | * Signal 4 Extension 0 |
>> > + | | * Count 7 |
>> > + +------------------------+------------------------+
>> > +
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-22 2:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 12:37 [PATCH v15 00/13] Introduce the Counter character device interface William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 01/13] counter: 104-quad-8: Describe member 'lock' in 'quad8' William Breathitt Gray
2021-08-09 19:26 ` Jonathan Cameron
2021-08-09 12:37 ` [PATCH v15 03/13] counter: Update counter.h comments to reflect sysfs internalization William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 04/13] docs: counter: Update " William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 05/13] counter: Move counter enums to uapi header William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 06/13] counter: Add character device interface William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 07/13] docs: counter: Document " William Breathitt Gray
2021-08-15 16:51 ` Jonathan Cameron
2021-08-21 10:52 ` William Breathitt Gray
2021-08-22 2:03 ` Akira Yokosawa [this message]
2021-08-09 12:37 ` [PATCH v15 08/13] tools/counter: Create Counter tools William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 09/13] counter: Implement signalZ_action_component_id sysfs attribute William Breathitt Gray
2021-08-15 16:57 ` Jonathan Cameron
2021-08-09 12:37 ` [PATCH v15 10/13] counter: Implement *_component_id sysfs attributes William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 11/13] counter: Implement events_queue_size sysfs attribute William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 12/13] counter: 104-quad-8: Replace mutex with spinlock William Breathitt Gray
2021-08-09 12:37 ` [PATCH v15 13/13] counter: 104-quad-8: Add IRQ support for the ACCES 104-QUAD-8 William Breathitt Gray
2021-08-09 19:34 ` [PATCH v15 00/13] Introduce the Counter character device interface Jonathan Cameron
[not found] ` <9844c0b2845fc001f64ebb0a4bc6d7fb7a08571a.1628511445.git.vilhelm.gray@gmail.com>
2021-08-15 16:31 ` [PATCH v15 02/13] counter: Internalize sysfs interface code Jonathan Cameron
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=f6930072-c487-a102-931c-53a79515d5fa@gmail.com \
--to=akiyks@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=vilhelm.gray@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).