public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "O'Rourke, Tom" <Tom.O'Rourke@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/chv: WaDisablePwrmtrEvent:chv on CHV only
Date: Tue, 10 Jun 2014 22:15:36 +0300	[thread overview]
Message-ID: <20140610191536.GH27580@intel.com> (raw)
In-Reply-To: <411E5DC12A51ED4CB1159E14310E532B9D8C3FC4@FMSMSX119.amr.corp.intel.com>

On Tue, Jun 10, 2014 at 07:03:48PM +0000, O'Rourke, Tom wrote:
> >> This is just a merge mishap in one the chv patches. Someone just needs
> >> to send a patch that moves the misapplied stuff to the appropriate chv
> >> function.
> >
> >Right. So my first comment was correct, and my elaboration total bullcrap. This
> >is not present in 3.15, but we've queued the screwup for 3.16. Thanks for the
> >correction Ville.
> >
> >BR,
> >Jani.
> >
> >
> >
> >>
> >> --
> >> Ville Syrjälä
> >> Intel OTC
> >
> >--
> >Jani Nikula, Intel Open Source Technology Center
> [TOR:] Hi Ville,
> Do you want to be the someone to send the patch that moves the misapplied stuff?

Go ahead if you want to do it. Easy +1 to your patch statistics ;)

> I could guess where it goes

Or just look at the original patch:
http://patchwork.freedesktop.org/patch/23974/

> but I do not have a CHV for testing the fix.\

You're not alone in that. In any case the patch was never really
tested, except by the compiler :P

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-06-10 19:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 17:06 [PATCH] drm/i915/chv: WaDisablePwrmtrEvent:chv on CHV only Tom.O'Rourke
2014-06-09 17:32 ` Damien Lespiau
2014-06-10 15:30   ` Jani Nikula
2014-06-10 15:34     ` Jani Nikula
2014-06-10 17:16       ` Ville Syrjälä
2014-06-10 18:17         ` Jani Nikula
2014-06-10 19:03           ` O'Rourke, Tom
2014-06-10 19:15             ` Ville Syrjälä [this message]
2014-06-10 23:26             ` [PATCH] drm/i915/chv: Fix "drm/i915/chv: Add a bunch of pre production workarounds" Tom.O'Rourke
2014-06-12  8:20               ` Ville Syrjälä
2014-06-12 10:35                 ` Daniel Vetter
2014-06-12 10:33           ` [PATCH] drm/i915/chv: WaDisablePwrmtrEvent:chv on CHV only Jani Nikula
2014-06-12 12:42             ` Daniel Vetter
2014-06-13  8:35               ` [PATCH] drm/i915/bdw: remove erroneous chv specific workarounds from bdw code Jani Nikula
2014-06-13  8:53                 ` Jani Nikula
2014-06-13 15:55                 ` O'Rourke, Tom

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=20140610191536.GH27580@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=Tom.O'Rourke@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