From: Sean Paul <sean@poorly.run>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: Fixes that failed to apply to v5.0-rc5
Date: Thu, 7 Feb 2019 16:26:09 -0500 [thread overview]
Message-ID: <20190207212609.GH114153@art_vandelay> (raw)
In-Reply-To: <87o97p75k3.fsf@intel.com>
On Wed, Feb 06, 2019 at 09:13:32AM +0200, Jani Nikula wrote:
> On Tue, 05 Feb 2019, Ville Syrjälä <ville.syrjala@linux.intel.com> 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:
> >> 32db0b6501d9 ("drm/i915: Don't try to use the hardware frame counter with i965gm TV output")
> >
> > This one depends on d20151a7699 ("drm/vblank: Allow dynamic per-crtc
*ed20151a7699
Is it being used in -misc-next right now? If not, perhaps revert there and apply to -intel-fixes? It doesn't look like it's landed in stable either.
....or just cherry-pick and make sure everything drops out nicely :)
Sean
> > max_vblank_count") which I seem to have pushed to drm-misc-next.
> >
> > Is it OK if we just cherry-pick that into drm-intel-fixes? Dave / Daniel?
>
> Ping. Also Cc: drm-misc maintainers.
>
> BR,
> Jani.
>
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-07 21:26 UTC|newest]
Thread overview: 11+ 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-05 14:18 ` 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 [this message]
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
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=20190207212609.GH114153@art_vandelay \
--to=sean@poorly.run \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=maxime.ripard@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.