From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Jani Nikula <jani.nikula@intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
"linux-doc@vger.kernel.org Mailing List"
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] doc-rst:c-domain: fix some issues in the c-domain
Date: Tue, 20 Sep 2016 17:58:11 -0300 [thread overview]
Message-ID: <20160920175811.71f8b899@vento.lan> (raw)
In-Reply-To: <20160920130033.6bb8668d@lwn.net>
Em Tue, 20 Sep 2016 13:00:33 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Tue, 20 Sep 2016 20:56:35 +0200
> Markus Heiser <markus.heiser@darmarit.de> wrote:
>
> > > I submitted one patch fixing it. Not sure if it got merged by Jon
> > > or not.
> >
> > Ups, I might have overseen this patch .. as Jon said, its hard to
> > follow you ;)
> >
> > I tested the above with Jon's docs-next, so it seems your patch is
> > not yet applied. Could you send me a link for this patch? (sorry,
> > I can't find it).
>
> Send again, please? I'll add it to the pile of other stuff, and try not
> to lose it again...:)
Gah, there are so many patches that I'm also confused whether I sent something
or just dreamed about sending it :)
I actually sent a patch doing this on a /47 patch series, but only
for macros:
Subject: [PATCH 01/47] kernel-doc: ignore arguments on macro definitions
I was thinking on doing the same for functions, but didn't actually
submitted such patch.
Yet, it seems more coherent, IMHO, to use use same approach for both C
functions and macros: presenting just the name instead of printing the
arguments.
I'll work on it and submit, likely tomorrow.
Thanks,
Mauro
next prev parent reply other threads:[~2016-09-20 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:12 [PATCH v2 0/3] doc-rst:c-domain: fix some issues in the c-domain Markus Heiser
2016-09-07 7:12 ` [PATCH v2 1/3] doc-rst:c-domain: fix sphinx version incompatibility Markus Heiser
2016-09-07 7:12 ` [PATCH v2 2/3] doc-rst:c-domain: function-like macros arguments Markus Heiser
2016-09-07 7:12 ` [RFC v2 3/3] doc-rst:c-domain: function-like macros index entry Markus Heiser
2016-09-09 12:08 ` [PATCH v2 0/3] doc-rst:c-domain: fix some issues in the c-domain Mauro Carvalho Chehab
2016-09-09 12:25 ` Markus Heiser
2016-09-19 11:36 ` Markus Heiser
2016-09-19 15:00 ` Mauro Carvalho Chehab
2016-09-20 18:56 ` Markus Heiser
2016-09-20 19:00 ` Jonathan Corbet
2016-09-20 20:58 ` Mauro Carvalho Chehab [this message]
2016-09-22 12:08 ` Mauro Carvalho Chehab
2016-09-22 12:35 ` kernel-lintdoc parser - was: " Mauro Carvalho Chehab
2016-09-22 22:03 ` Markus Heiser
2016-09-22 23:58 ` Markus Heiser
2016-09-16 16:02 ` Jonathan Corbet
2016-09-17 9:45 ` Markus Heiser
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=20160920175811.71f8b899@vento.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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).