public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	markus.heiser@darmarit.de, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Documentation/sphinx: link dma-buf rsts
Date: Tue, 23 Aug 2016 07:08:18 -0600	[thread overview]
Message-ID: <20160823070818.42ffec00@lwn.net> (raw)
In-Reply-To: <20160823060135.GJ24290@phenom.ffwll.local>

On Tue, 23 Aug 2016 08:01:35 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:

> I'm also not too sure about whether dma-buf really should be it's own
> subdirectory. It's plucked from the device-drivers.tmpl, I think an
> overall device-drivers/ for all the misc subsystems and support code would
> be better. Then one toc there, which fans out to either kernel-doc and
> overview docs.

I'm quite convinced it shouldn't be.

If you get a chance, could you have a look at the "RFC: The beginning of
a proper driver-api book" series I posted yesterday (yes, I should have
copied more of you, sorry)?  It shows the direction I would like to go
with driver API documentation, and, assuming we go that way, I'd like the
dma-buf documentation to fit into that.

Thanks,

jon

  parent reply	other threads:[~2016-08-23 13:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 15:11 [PATCH v2 0/2] doc: dma-buf: sphinx conversion Sumit Semwal
2016-08-22 15:11 ` [PATCH v2 1/2] Documentation: move dma-buf documentation to rst Sumit Semwal
2016-08-22 15:11 ` [PATCH v2 2/2] Documentation/sphinx: link dma-buf rsts Sumit Semwal
2016-08-22 15:49   ` Mauro Carvalho Chehab
2016-08-23  6:01     ` Daniel Vetter
2016-08-23  9:20       ` Markus Heiser
2016-08-23 13:08       ` Jonathan Corbet [this message]
2016-08-23 13:28         ` Daniel Vetter
2016-08-23 14:16           ` Jonathan Corbet
2016-08-23 15:15             ` Daniel Vetter
2016-08-23 16:40             ` Mauro Carvalho Chehab
2016-08-23 13:33         ` Sumit Semwal

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=20160823070818.42ffec00@lwn.net \
    --to=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@s-opensource.com \
    --cc=sumit.semwal@linaro.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