From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
Matthew Wilcox <willy@infradead.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters
Date: Tue, 26 Jun 2018 08:59:13 -0600 [thread overview]
Message-ID: <20180626085913.6094bdc6@lwn.net> (raw)
In-Reply-To: <20180620084911.GB11493@rapoport-lnx>
On Wed, 20 Jun 2018 11:49:12 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> > Looks good to me. Though I do realize now that I overlooked that this
> > applies to not only functions, but also to other non-DOC documentation
> > comments. I guess up to Jon to decide.
>
> We can name it "everything-except-doc-sections" ;-)
I suppose it could be :code: or :declarations: or some such. But I think
I'm inclined to just apply the patches as they are. The handling of
structs and such has always been a bit bolted onto the side, this doesn't
really change anything.
(Sorry for my absence in general - took some much-needed offline time).
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-26 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 4:21 [PATCH v2 0/2] Documentation/sphinx: add kind of "nodocs" directive Mike Rapoport
2018-06-20 4:21 ` [PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters Mike Rapoport
2018-06-20 7:19 ` Jani Nikula
2018-06-20 8:49 ` Mike Rapoport
2018-06-26 14:59 ` Jonathan Corbet [this message]
2018-06-20 4:21 ` [PATCH v2 2/2] docs/idr: use empty "functions" directive Mike Rapoport
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=20180626085913.6094bdc6@lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=willy@infradead.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