From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Rogovin, Kevin" <kevin.rogovin@intel.com>,
"abdiel.janulgue@linux.intel.com"
<abdiel.janulgue@linux.intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>
Subject: Re: [PATCH v4 5/5] i915: add documentation to intel_engine_cs
Date: Wed, 04 Apr 2018 14:59:06 +0300 [thread overview]
Message-ID: <87vad7faid.fsf@intel.com> (raw)
In-Reply-To: <152283762218.10680.2726250608726441252@jlahtine-desk.ger.corp.intel.com>
On Wed, 04 Apr 2018, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
> To be perfectly clear: Are we working towards a clean make htmldocs and
> CI nagging when it gets broken?
I'd like that to be the goal, yes. I'm not sure if anyone's working
towards that.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-04 11:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 10:52 [PATCH v4 0/5] Documentation patch for batchbuffer submission kevin.rogovin
2018-04-03 10:52 ` [PATCH v4 1/5] i915.rst: Narration overview on GEM + minor reorder to improve narration kevin.rogovin
2018-04-03 12:07 ` Joonas Lahtinen
2018-04-03 13:31 ` Jani Nikula
2018-04-03 13:55 ` Mika Kuoppala
2018-04-04 7:56 ` Mika Kuoppala
2018-04-04 22:22 ` Belgaumkar, Vinay
2018-04-03 10:52 ` [PATCH v4 2/5] i915: add a text about what happens at bottom of stack in processing a batchbuffer kevin.rogovin
2018-04-03 12:15 ` Joonas Lahtinen
2018-04-03 10:52 ` [PATCH v4 3/5] i915.rst: add link to documentation in i915_gem_execbuffer.c kevin.rogovin
2018-04-03 12:16 ` Joonas Lahtinen
2018-04-03 10:52 ` [PATCH v4 4/5] i915: correct lazy ringbuffer and backing store documentation kevin.rogovin
2018-04-03 10:52 ` [PATCH v4 5/5] i915: add documentation to intel_engine_cs kevin.rogovin
2018-04-03 13:10 ` Joonas Lahtinen
2018-04-03 14:34 ` Rogovin, Kevin
2018-04-04 9:31 ` Joonas Lahtinen
2018-04-04 9:48 ` Jani Nikula
2018-04-04 10:27 ` Joonas Lahtinen
2018-04-04 11:59 ` Jani Nikula [this message]
2018-04-03 12:19 ` ✗ Fi.CI.BAT: failure for Documentation patch for batchbuffer submission (rev4) Patchwork
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=87vad7faid.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=abdiel.janulgue@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.rogovin@intel.com \
--cc=tvrtko.ursulin@linux.intel.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