All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Matthew Wilcox <mawilcox@microsoft.com>,
	Tom Saeger <tom.saeger@oracle.com>,
	Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	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: [PATCH 0/6] Add support for in-line nested struct comments
Date: Sun, 18 Feb 2018 17:03:34 -0700	[thread overview]
Message-ID: <20180218170334.711d50e2@lwn.net> (raw)
In-Reply-To: <cover.1518788761.git.mchehab@s-opensource.com>

On Fri, 16 Feb 2018 11:48:14 -0200
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:

> his 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.

OK, I've applied everything but the last patch, which I assume will go
through the DRM tree.

Thanks,

jon
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Tom Saeger <tom.saeger@oracle.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Matthew Wilcox <mawilcox@microsoft.com>,
	intel-gfx@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/6] Add support for in-line nested struct comments
Date: Sun, 18 Feb 2018 17:03:34 -0700	[thread overview]
Message-ID: <20180218170334.711d50e2@lwn.net> (raw)
In-Reply-To: <cover.1518788761.git.mchehab@s-opensource.com>

On Fri, 16 Feb 2018 11:48:14 -0200
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:

> his 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.

OK, I've applied everything but the last patch, which I assume will go
through the DRM tree.

Thanks,

jon

  parent reply	other threads:[~2018-02-19  0:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 13:48 [PATCH 0/6] Add support for in-line nested struct comments Mauro Carvalho Chehab
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-16 13:48   ` Mauro Carvalho Chehab
2018-02-19  0:03 ` Jonathan Corbet [this message]
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 10:05     ` Jani Nikula
2018-02-19 15:39 ` Daniel Vetter
2018-02-19 15:39   ` [Intel-gfx] " Daniel Vetter

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=20180218170334.711d50e2@lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@linux.ie \
    --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 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.