From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com,
Pandiyan Dhinakaran <dhinakaran.pandiyan@intel.com>
Subject: [PATCH v2 0/3] drm/i915: add register macro definition style guide
Date: Thu, 10 Aug 2017 15:29:41 +0300 [thread overview]
Message-ID: <cover.1502368010.git.jani.nikula@intel.com> (raw)
This is v2 of [1], with minor tweaks and bolting the document into the
Sphinx build.
BR,
Jani.
[1] http://patchwork.freedesktop.org/patch/msgid/20170804103836.17629-1-jani.nikula@intel.com
Jani Nikula (3):
Documentation/i915: remove sphinx conversion artefact
drm/i915: enum i915_power_well_id is not proper kernel-doc
drm/i915: add register macro definition style guide
Documentation/gpu/i915.rst | 14 ++++++-
drivers/gpu/drm/i915/i915_reg.h | 93 ++++++++++++++++++++++++++++++++++++++++-
2 files changed, 105 insertions(+), 2 deletions(-)
--
2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-08-10 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 12:29 Jani Nikula [this message]
2017-08-10 12:29 ` [PATCH v2 1/3] Documentation/i915: remove sphinx conversion artefact Jani Nikula
2017-08-10 15:19 ` Rodrigo Vivi
2017-08-10 16:13 ` Jani Nikula
2017-08-10 19:31 ` Rodrigo Vivi
2017-08-10 12:29 ` [PATCH v2 2/3] drm/i915: enum i915_power_well_id is not proper kernel-doc Jani Nikula
2017-08-10 15:17 ` Rodrigo Vivi
2017-08-10 12:29 ` [PATCH v2 3/3] drm/i915: add register macro definition style guide Jani Nikula
2017-08-10 12:55 ` ✗ Fi.CI.BAT: failure for drm/i915: add register macro definition style guide (rev2) Patchwork
2017-08-10 20:11 ` Jani Nikula
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=cover.1502368010.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.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