From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, linux-doc@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix documentation build warnings
Date: Wed, 05 Jun 2019 15:35:04 +0300 [thread overview]
Message-ID: <877ea0rz0n.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190605095657.23601-2-jani.nikula@intel.com>
Jani Nikula <jani.nikula@intel.com> writes:
> Just a straightforward bag of fixes for a clean htmldocs build.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
next prev parent reply other threads:[~2019-06-05 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:56 [PATCH 1/2] Documentation/i915: Fix kernel-doc references to moved gem files Jani Nikula
2019-06-05 9:56 ` [PATCH 2/2] drm/i915: fix documentation build warnings Jani Nikula
2019-06-05 12:35 ` Mika Kuoppala [this message]
2019-06-05 10:29 ` [PATCH 1/2] Documentation/i915: Fix kernel-doc references to moved gem files Mika Kuoppala
2019-06-06 8:23 ` 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=877ea0rz0n.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).