From: Jani Nikula <jani.nikula@linux.intel.com>
To: Oscar Mateo <oscar.mateo@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 1/2] drm/i915: Move a bunch of workaround-related code to its own file
Date: Mon, 26 Feb 2018 12:16:57 +0200 [thread overview]
Message-ID: <87k1v02gyu.fsf@intel.com> (raw)
In-Reply-To: <1519423421-28244-1-git-send-email-oscar.mateo@intel.com>
On Fri, 23 Feb 2018, Oscar Mateo <oscar.mateo@intel.com> wrote:
> diff --git a/drivers/gpu/drm/i915/intel_workarounds.c b/drivers/gpu/drm/i915/intel_workarounds.c
> new file mode 100644
> index 0000000..bd23418
> --- /dev/null
> +++ b/drivers/gpu/drm/i915/intel_workarounds.c
> @@ -0,0 +1,684 @@
> +/*
> + * SPDX-License-Identifier: MIT
> + *
> + * Copyright © 2014-2018 Intel Corporation
> + */
> +
> +#include "i915_drv.h"
> +#include "intel_workarounds.h"
> +
> +/**
> + * DOC: Hardware workarounds
Please include this in the documentation build. (Add a suitable
kernel-doc directive in i915.rst.)
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-02-26 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 22:03 [PATCH v5 1/2] drm/i915: Move a bunch of workaround-related code to its own file Oscar Mateo
2018-02-23 22:03 ` [PATCH v5 2/2] drm/i915: Split out functions for different kinds of workarounds Oscar Mateo
2018-02-23 22:08 ` ✗ Fi.CI.SPARSE: warning for series starting with [v5,1/2] drm/i915: Move a bunch of workaround-related code to its own file Patchwork
2018-02-23 22:25 ` ✗ Fi.CI.BAT: " Patchwork
2018-02-26 10:16 ` Jani Nikula [this message]
2018-02-26 23:01 ` [PATCH v6 1/2] " Oscar Mateo
2018-02-26 23:20 ` Chris Wilson
2018-02-27 10:06 ` Jani Nikula
2018-02-26 23:36 ` ✗ Fi.CI.SPARSE: warning for series starting with [v6,1/2] drm/i915: Move a bunch of workaround-related code to its own file (rev2) Patchwork
2018-02-26 23:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-27 2:54 ` ✓ Fi.CI.IGT: " 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=87k1v02gyu.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@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;
as well as URLs for NNTP newsgroup(s).