From: Wolfram Sang <wsa@the-dreams.de>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-input@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH v4 3/6] i2c: add docs to clarify DMA handling
Date: Wed, 20 Sep 2017 19:18:40 +0200 [thread overview]
Message-ID: <20170920171840.nrzyiasezxisvg5m@ninjato> (raw)
In-Reply-To: <20170827083748.248e2430@vento.lan>
[-- Attachment #1.1: Type: text/plain, Size: 887 bytes --]
Hi Mauro,
> > +Linux I2C and DMA
> > +-----------------
>
> I would use, instead:
>
> =================
> Linux I2C and DMA
> =================
>
> As this is the way we're starting document titles, after converted to
> ReST. So, better to have it already using the right format, as one day
I did this.
> There are also a couple of things here that Sphinx would complain.
The only complaint I got was
WARNING: document isn't included in any toctree
which makes sense because I renamed it only temporarily to *.rst
> So, it could be worth to rename it to *.rst, while you're writing
> it, and see what:
> make htmldocs
> will complain and how it will look in html.
So, no complaints from Sphinx and the HTML output looks good IMO. Was
there anything specific you had in mind when saying that Sphinx would
complain?
Regards,
Wolfram
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-20 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:14 [RFC PATCH v4 0/6] i2c: document DMA handling and add helpers for it Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 1/6] i2c: add a message flag for DMA safe buffers Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 2/6] i2c: add helpers to ease DMA handling Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 3/6] i2c: add docs to clarify " Wolfram Sang
2017-08-27 11:37 ` Mauro Carvalho Chehab
2017-09-08 8:56 ` Wolfram Sang
2017-09-08 11:08 ` Mauro Carvalho Chehab
2017-09-09 15:27 ` Wolfram Sang
2017-09-09 19:34 ` Mauro Carvalho Chehab
2017-09-20 17:18 ` Wolfram Sang [this message]
2017-09-20 18:22 ` Mauro Carvalho Chehab
2017-09-20 18:45 ` Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 4/6] i2c: sh_mobile: use helper to decide if DMA is useful Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 5/6] i2c: rcar: skip DMA if buffer is not safe Wolfram Sang
2017-08-17 14:14 ` [RFC PATCH v4 6/6] i2c: dev: mark RDWR buffers as DMA_SAFE Wolfram Sang
2017-08-20 10:14 ` [RFC PATCH v4 0/6] i2c: document DMA handling and add helpers for it Jonathan Cameron
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=20170920171840.nrzyiasezxisvg5m@ninjato \
--to=wsa@the-dreams.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=wsa+renesas@sang-engineering.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