From: Daniel Vetter <daniel@ffwll.ch>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org,
Tom Saeger <tom.saeger@oracle.com>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/6] Add support for in-line nested struct comments
Date: Mon, 19 Feb 2018 16:39:13 +0100 [thread overview]
Message-ID: <20180219153913.GU22199@phenom.ffwll.local> (raw)
In-Reply-To: <cover.1518788761.git.mchehab@s-opensource.com>
On Fri, Feb 16, 2018 at 11:48:14AM -0200, Mauro Carvalho Chehab wrote:
> This series fix two bugs at kernel-doc.rst examples and add support
> for in-line nested struct comments.
>
> It also converts one documentation at intel_dpio_phy to use it,
> in order to give a practical example about how to use it.
>
> Mauro Carvalho Chehab (6):
> doc-guide: kernel-doc: fix example for nested_foobar struct
> doc-guide: kernel-doc: fix example for inlined comments
> doc-guide: kernel-doc: move in-line section to be after nested struct
> scripts: kernel-doc: support in-line comments on nested structs/unions
> doc-guide: kernel-doc: add examples about nested union/structs
> drm: intel_dpio_phy: fix kernel-doc comments at nested struct
Oh, this is cool. Thanks a lot for doing this.
-Daniel
>
> Documentation/doc-guide/kernel-doc.rst | 69 ++++++++++++++++++++--------------
> drivers/gpu/drm/i915/intel_dpio_phy.c | 2 +-
> scripts/kernel-doc | 2 +-
> 3 files changed, 43 insertions(+), 30 deletions(-)
>
> --
> 2.14.3
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2018-02-19 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 13:48 Mauro Carvalho Chehab
2018-02-16 13:48 ` [PATCH 1/6] doc-guide: kernel-doc: fix example for nested_foobar struct Mauro Carvalho Chehab
2018-02-16 13:48 ` [PATCH 2/6] doc-guide: kernel-doc: fix example for inlined comments Mauro Carvalho Chehab
2018-02-16 13:48 ` [PATCH 3/6] doc-guide: kernel-doc: move in-line section to be after nested struct Mauro Carvalho Chehab
2018-02-16 13:48 ` [PATCH 4/6] scripts: kernel-doc: support in-line comments on nested structs/unions Mauro Carvalho Chehab
2018-02-16 14:52 ` Markus Heiser
2018-02-16 14:56 ` Mauro Carvalho Chehab
2018-02-16 16:11 ` Markus Heiser
2018-02-16 13:48 ` [PATCH 5/6] doc-guide: kernel-doc: add examples about nested union/structs Mauro Carvalho Chehab
2018-02-16 13:48 ` [PATCH 6/6] drm: intel_dpio_phy: fix kernel-doc comments at nested struct Mauro Carvalho Chehab
2018-02-19 0:03 ` [PATCH 0/6] Add support for in-line nested struct comments Jonathan Corbet
2018-02-19 10:05 ` Jani Nikula
2018-02-19 15:39 ` Daniel Vetter [this message]
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=20180219153913.GU22199@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
--cc=rodrigo.vivi@intel.com \
--cc=tom.saeger@oracle.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
Powered by JetHome