public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Aditya Swarup <aditya.swarup@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Fixes that failed to apply to v5.0-rc5
Date: Fri, 8 Feb 2019 09:51:53 -0800	[thread overview]
Message-ID: <20190208175153.GA32231@intel.com> (raw)
In-Reply-To: <20190208130751.GA22554@aswarup-desk>

On Fri, Feb 08, 2019 at 05:07:52AM -0800, Aditya Swarup wrote:
> On Tue, Feb 05, 2019 at 03:42:05PM +0200, Jani Nikula wrote:
> > 
> > The following commits have been marked as Cc: stable or fixing something
> > in v5.0-rc5 or earlier, but failed to cherry-pick to
> > drm-intel-fixes. Please see if they are worth backporting, and please do
> > so if they are.
> > 
> > Failed to cherry-pick:
> > b14c06ec0249 ("drm/i915/cnl: Fix CNL macros for Voltage Swing programming")
> b14c06ec0249 is dependent on 
> 265a2a6255f5 drm/i915/icl: combo port vswing programming changes per BSPEC

It is actually b265a2a6255f5
b265a2a6255f ("drm/i915/icl: combo port vswing programming changes per BSPEC")

> https://patchwork.freedesktop.org/patch/268514/
> 
> How should I go about the backport to drm-intel-fixes?

Nothing. Well, you already did by providing the dependency ;)

Jani could cherry-pick both because
both applies cleanly on drm-intel-fixes

> 
> > 32db0b6501d9 ("drm/i915: Don't try to use the hardware frame counter with i965gm TV output")
> > 
> > Cherry-pick fine but fail to build:
> > 7bed8adcd9f8 ("drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen")
> > 
> > BR,
> > Jani.
> > 
> > 
> > -- 
> > Jani Nikula, Intel Open Source Graphics Center
> 
> Regards,
> Aditya Swarup
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2019-02-08 17:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 13:42 Fixes that failed to apply to v5.0-rc5 Jani Nikula
2019-02-05 14:18 ` [PATCH -fixes] drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen Ville Syrjala
2019-02-06  7:11   ` [Intel-gfx] " Jani Nikula
2019-02-07 16:32   ` Sasha Levin
2019-02-05 14:23 ` Fixes that failed to apply to v5.0-rc5 Ville Syrjälä
2019-02-06  7:13   ` Jani Nikula
2019-02-07 21:26     ` Sean Paul
2019-02-05 16:01 ` ✗ Fi.CI.BAT: failure for drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen (rev3) Patchwork
2019-02-08 13:07 ` Fixes that failed to apply to v5.0-rc5 Aditya Swarup
2019-02-08 17:51   ` Rodrigo Vivi [this message]

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=20190208175153.GA32231@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=aditya.swarup@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox