From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 3/3] drm/i915: Add early BXT sdv to the list of preproduction machines
Date: Mon, 30 Jan 2017 14:36:56 +0200 [thread overview]
Message-ID: <1485779816.2893.8.camel@linux.intel.com> (raw)
In-Reply-To: <20170130104458.2653-3-chris@chris-wilson.co.uk>
On ma, 2017-01-30 at 10:44 +0000, Chris Wilson wrote:
> Extend intel_detect_preproduction_hw() to include BXT A and B steppings.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-30 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 10:44 [PATCH v2 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Chris Wilson
2017-01-30 10:44 ` [PATCH v2 2/3] drm/i915: Mark the kernel as tainted if we fail the preproduction check Chris Wilson
2017-01-30 12:31 ` Joonas Lahtinen
2017-01-30 13:25 ` Chris Wilson
2017-01-30 10:44 ` [PATCH v2 3/3] drm/i915: Add early BXT sdv to the list of preproduction machines Chris Wilson
2017-01-30 12:36 ` Joonas Lahtinen [this message]
2017-01-30 12:35 ` [PATCH v2 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Joonas Lahtinen
2017-01-30 13:11 ` Jani Nikula
2017-01-30 13:18 ` Chris Wilson
2017-01-30 17:54 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/3] " Patchwork
2017-01-31 16:10 ` Chris Wilson
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=1485779816.2893.8.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.