All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Silvio Fricke <silvio.fricke@gmail.com>
Cc: linux-doc@vger.kernel.org, Ming Lei <ming.lei@canonical.com>,
	"Luis R . Rodriguez" <mcgrof@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops
Date: Wed, 30 Nov 2016 17:51:29 -0700	[thread overview]
Message-ID: <20161130175129.5ab7158f@lwn.net> (raw)
In-Reply-To: <cover.a9f60820422cef425c9ebeb73a41c5378a43ce88.1480354075.git-series.silvio.fricke@gmail.com>

On Mon, 28 Nov 2016 18:30:52 +0100
Silvio Fricke <silvio.fricke@gmail.com> wrote:

> Some more ReSTification of core-api's: assoc_array, atomic_ops and local_ops. A
> fourth patch removes a warning about a bullet list without ending at
> firmware_class.c

OK, I've merged patches 1-3.  Peter, if you ever want to edit atomic_ops,
just send it meward when you're done and I'll deal with any formatting
issues.

Silvio, if you wanted to take this further, the assoc_array code is
nicely decorated with kerneldoc comments; using those in the
documentation would be a nice thing.  There are some kerneldoc comments
for the atomic functions, but that seems rather more erratic.

Part 4 (firmware_class.c) is a bit off my turf, so I don't think I can
apply it.  From what I can tell looking at the history, Andrew Morton
might be a logical target for that patch.

Thanks,

jon

  parent reply	other threads:[~2016-12-01  0:51 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 12:42 [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-24 12:42 ` [PATCH 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-24 12:42 ` [PATCH 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-24 19:46 ` [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 " Silvio Fricke
2016-11-25 10:02   ` [PATCH v2 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 13:03     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 13:25     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 13:47       ` S. Fricke
2016-11-25 13:58         ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 14:59   ` [PATCH v3 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-25 14:59     ` [PATCH v3 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 20:53       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 21:01       ` Mauro Carvalho Chehab
2016-11-25 21:58       ` Peter Zijlstra
2016-11-27 14:53         ` S. Fricke
2016-11-27 18:36           ` Jani Nikula
2016-11-27 23:59         ` Jonathan Corbet
2016-11-28  7:26           ` Peter Zijlstra
2016-11-28  8:44             ` Daniel Vetter
2016-11-28 10:20               ` Peter Zijlstra
2016-11-28 11:08                 ` Mauro Carvalho Chehab
2016-11-28 11:54                   ` Peter Zijlstra
2016-11-28 13:46                     ` Daniel Vetter
2016-11-28 15:14                       ` Mauro Carvalho Chehab
2016-11-28 11:16                 ` Jani Nikula
2016-11-28 11:56                   ` Peter Zijlstra
2016-11-28 12:32                     ` Jani Nikula
2016-11-28 14:13                 ` Daniel Vetter
2016-11-28 14:29                   ` Jonathan Corbet
2016-11-25 14:59     ` [PATCH v3 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 21:10       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 20:50       ` Mauro Carvalho Chehab
2016-12-01 16:11         ` Luis R. Rodriguez
2016-12-01 16:45           ` Greg Kroah-Hartman
2016-11-28 17:30     ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 2/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 3/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-12-01  0:51       ` Jonathan Corbet [this message]
2016-12-01 15:49         ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Luis R. Rodriguez

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=20161130175129.5ab7158f@lwn.net \
    --to=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=peterz@infradead.org \
    --cc=silvio.fricke@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.