public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	alexander.levin@verizon.com,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV
Date: Fri, 17 Nov 2017 14:58:42 +0100	[thread overview]
Message-ID: <20171117135842.GC10105@kroah.com> (raw)
In-Reply-To: <CACvgo50=M4pvjOF57KxQyQw52WKnJX+tdBwZoALYgVmUdrqf5g@mail.gmail.com>

On Fri, Nov 17, 2017 at 01:13:27PM +0000, Emil Velikov wrote:
> Hi Greg, all,
> 
> Pardon for the silly question, but I'm struggling to find
> documentation about this new 'autoselection' process?
> Where can one read up on it - be that about the tooling or the heuristics used?
> 
> I think the above may be the core reason behind the discussion here.

See my other email on this topic already (hint, it shouldn't matter how
the patch is selected if at least one experienced developer feels it
might be a valid stable patch...)

thanks,

greg k-h
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-17 13:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171115024521.5884-1-alexander.levin@verizon.com>
     [not found] ` <20171115024521.5884-36-alexander.levin@verizon.com>
     [not found]   ` <20171115110805.GX10981@intel.com>
     [not found]     ` <20171115164451.ogl3ku6qr3cfnbk7@sasha-lappy>
2017-11-15 17:03       ` [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV Ville Syrjälä
2017-11-17 11:28         ` Jani Nikula
2017-11-17 12:41           ` Greg KH
2017-11-17 12:53             ` Ville Syrjälä
2017-11-17 12:59               ` Greg KH
2017-11-17 13:13                 ` Emil Velikov
2017-11-17 13:58                   ` Greg KH [this message]
2017-11-17 13:01             ` Jani Nikula
2017-11-17 13:57               ` Greg KH
2017-11-18  3:15               ` alexander.levin

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=20171117135842.GC10105@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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