From: Jonathan Corbet <corbet@lwn.net>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup
Date: Thu, 11 Aug 2016 08:36:52 -0600 [thread overview]
Message-ID: <20160811083652.55371952@lwn.net> (raw)
In-Reply-To: <1470912480-32304-1-git-send-email-sumit.semwal@linaro.org>
On Thu, 11 Aug 2016 16:17:56 +0530
Sumit Semwal <sumit.semwal@linaro.org> wrote:
> Convert dma-buf documentation over to sphinx; also cleanup to
> address sphinx warnings.
>
> While at that, convert dma-buf-sharing.txt as well, and make it the
> dma-buf API guide.
Thanks for working to improve the documentation! I do have a few overall
comments...
- The two comment fixes are a separate thing that should go straight to
the dma-buf maintainer, who is ... <looks> ... evidently somebody
familiar to you :) I assume you'll merge those two directly?
- It looks like you create a new RST document but leave the old one in
place. Having two copies of the document around can only lead to
confusion, so I think the old one should go.
- I really wonder if we want to start carving pieces out of
device-drivers.tmpl in this way. I guess I would rather see the
conversion of that book and the better integration of the other docs
*into* it. One of the goals of this whole thing is to unify our
documentation, not to reinforce the silos.
Does that make sense?
Thanks,
jon
next prev parent reply other threads:[~2016-08-11 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 10:47 [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal
2016-08-11 10:47 ` [RFC 1/4] dma-buf/fence: kerneldoc: remove unused struct members Sumit Semwal
2016-08-11 10:47 ` [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Sumit Semwal
2016-08-12 8:44 ` Daniel Vetter
2016-08-11 10:47 ` [RFC 3/4] Documentation: move dma-buf documentation to rst Sumit Semwal
2016-08-11 11:47 ` Jani Nikula
2016-08-11 12:31 ` Sumit Semwal
2016-08-11 11:58 ` Markus Heiser
2016-08-11 12:12 ` Markus Heiser
2016-08-11 12:49 ` Sumit Semwal
2016-08-11 10:48 ` [RFC 4/4] Documentation/sphinx: link dma-buf rsts Sumit Semwal
2016-08-11 14:36 ` Jonathan Corbet [this message]
2016-08-12 6:35 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal
2016-08-12 8:38 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2016-08-11 10:45 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=20160811083652.55371952@lwn.net \
--to=corbet@lwn.net \
--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=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