From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.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: Wed, 06 Feb 2019 09:13:32 +0200 [thread overview]
Message-ID: <87o97p75k3.fsf@intel.com> (raw)
In-Reply-To: <20190205142347.GQ20097@intel.com>
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
> 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
_______________________________________________
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-06 7:12 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 [this message]
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
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=87o97p75k3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=ville.syrjala@linux.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