public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Heiser <markus.heiser@darmarit.de>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Markus Heiser <markus.heiser@darmarIT.de>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: [PATCH 3/3] doc-rst: add stand-alone conf.py to gpu folder
Date: Mon,  8 Aug 2016 15:15:00 +0200	[thread overview]
Message-ID: <1470662100-6927-4-git-send-email-markus.heiser@darmarit.de> (raw)
In-Reply-To: <1470662100-6927-1-git-send-email-markus.heiser@darmarit.de>

From: Markus Heiser <markus.heiser@darmarIT.de>

With the gpu/conf.py, the gpu folder can be build and distributed
stand-alone.

Signed-off-by: Markus Heiser <markus.heiser@darmarIT.de>
---
 Documentation/gpu/conf.py | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 Documentation/gpu/conf.py

diff --git a/Documentation/gpu/conf.py b/Documentation/gpu/conf.py
new file mode 100644
index 0000000..d60bcd0
--- /dev/null
+++ b/Documentation/gpu/conf.py
@@ -0,0 +1,3 @@
+# -*- coding: utf-8; mode: python -*-
+
+project = "Linux GPU Driver Developer's Guide"
-- 
2.7.4


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 13:14 [PATCH 0/3] doc-rst: more generic way to build only sphinx sub-folders Markus Heiser
2016-08-08 13:14 ` [PATCH 1/3] doc-rst: " Markus Heiser
2016-08-12 21:20   ` Jonathan Corbet
2016-08-13 14:38     ` Markus Heiser
2016-08-08 13:14 ` [PATCH 2/3] doc-rst: add stand-alone conf.py to media folder Markus Heiser
2016-08-08 13:15 ` Markus Heiser [this message]
2016-08-09 15:21 ` [PATCH 0/3] doc-rst: more generic way to build only sphinx sub-folders Jonathan Corbet
2016-08-09 18:02   ` Mauro Carvalho Chehab
2016-08-09 18:37     ` Markus Heiser

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=1470662100-6927-4-git-send-email-markus.heiser@darmarit.de \
    --to=markus.heiser@darmarit.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mchehab@s-opensource.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