stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
	intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gen9: unconditionally apply the memory bandwidth WA
Date: Tue, 11 Oct 2016 12:31:07 +0200	[thread overview]
Message-ID: <20161011103107.GA9793@kroah.com> (raw)
In-Reply-To: <87wphfqqyx.fsf@intel.com>

On Tue, Oct 11, 2016 at 10:34:14AM +0300, Jani Nikula wrote:
> On Mon, 10 Oct 2016, Paulo Zanoni <paulo.r.zanoni@intel.com> wrote:
> > Mahesh Kumar is already working on a proper implementation for the
> > workaround, but while we still don't have it, let's just
> > unconditionally apply the workaround for everybody and we hope we can
> > close all those numerous bugzilla tickets. Also, I'm not sure how easy
> > it will be to backport the final implementation to the stable Kernels,
> > and this patch here is probably easier to backport.
> >
> > At the present moment I still don't have confirmation that this patch
> > fixes any of the bugs listed below, but we should definitely try
> > testing all of them again.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94337
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94605
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94884
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95010
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96226
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96828
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97450
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97830
> > Cc: stable@vger.kernel.org
> 
> The patch is a bit on the large side for stable. 100 lines with context
> is the rule.

Huh?  It's only 49 line of changes:

> >  drivers/gpu/drm/i915/intel_pm.c | 49 ++++++++++++++++++++++++++++++++++-------
> >  1 file changed, 41 insertions(+), 8 deletions(-)

That's fine for stable, we take i915 stable patches much bigger than
that all the time :)

thanks,

greg k-h

  reply	other threads:[~2016-10-11 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 20:30 [PATCH 1/2] drm/i915/gen9: unconditionally apply the memory bandwidth WA Paulo Zanoni
2016-10-10 20:34 ` Lyude Paul
2016-10-10 20:46   ` Zanoni, Paulo R
2016-10-10 20:55     ` Lyude Paul
2016-10-11 18:25       ` Paulo Zanoni
2016-10-14 21:45         ` Lyude
2016-10-11  7:34 ` [Intel-gfx] " Jani Nikula
2016-10-11 10:31   ` Greg KH [this message]
2016-10-11 10:54     ` Jani Nikula
2016-10-11 11:10       ` Greg KH

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=20161011103107.GA9793@kroah.com \
    --to=greg@kroah.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=paulo.r.zanoni@intel.com \
    --cc=stable@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).