stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, tjaalton@ubuntu.com,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Manasi Navare <manasi.d.navare@intel.com>
Subject: Re: v4.13+ stable backport request
Date: Fri, 13 Apr 2018 11:48:02 +0300	[thread overview]
Message-ID: <87efjjfq65.fsf@intel.com> (raw)
In-Reply-To: <20180412150038.GA21890@kroah.com>

On Thu, 12 Apr 2018, Greg KH <greg@kroah.com> wrote:
> On Thu, Apr 12, 2018 at 02:46:17PM +0200, Greg KH wrote:
>> On Thu, Apr 12, 2018 at 12:09:40PM +0300, Jani Nikula wrote:
>> > 
>> > Stable team, please backport commit
>> > 
>> > a306343bcd7d ("drm/i915/edp: Do not do link training fallback or prune modes on EDP")
>> > 
>> > to v4.13+
>> > 
>> > Fixes: 9301397a63b3 ("drm/i915: Implement Link Rate fallback on Link training failure")
>> 
>> Now queued up, thanks.
>
> Nope, breaks the build in the 4.14.y tree, so I'm dropping it there.
> Please provide a working backport if you want it in that tree.

Damn, sorry. Timo, you requested the backport, what's your feeling on
v4.13 and v4.14?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2018-04-13  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12  9:09 v4.13+ stable backport request Jani Nikula
2018-04-12 12:46 ` Greg KH
2018-04-12 15:00   ` Greg KH
2018-04-13  8:48     ` Jani Nikula [this message]
2018-04-13  8:52       ` Greg KH
2018-04-13  8:55       ` Timo Aaltonen
2018-04-13 12:30         ` Jani Nikula

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=87efjjfq65.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=greg@kroah.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tjaalton@ubuntu.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).