From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915: fix HPD IRQ reenable work cancelation
Date: Mon, 18 Aug 2014 13:33:51 +0300 [thread overview]
Message-ID: <87bnrinl2o.fsf@intel.com> (raw)
In-Reply-To: <1408101999.20783.12.camel@intelbox>
On Fri, 15 Aug 2014, Imre Deak <imre.deak@intel.com> wrote:
> On Fri, 2014-08-15 at 12:48 +0300, Jani Nikula wrote:
>> On Fri, 15 Aug 2014, Imre Deak <imre.deak@intel.com> wrote:
>> > On Wed, 2014-08-13 at 19:33 +0300, Ville Syrjälä wrote:
>> >> The series seems fine to me.
>> >>
>> >> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> >> for the rest as well.
>> >
>> > Thanks, I assume it's for v2. I'd say this is for -fixes. The problem
>> > existed even in 3.16, but only the MST support made it apparent with the
>> > extra HPD signaling and DP AUX activity during suspend.
>>
>> The series no longer applies on any branch. Would you mind respinning on
>> -fixes please?
>
> Ok. I just noticed that it depends on the following two patches that are
> only in -nightly not in -fixes:
>
> "drm/i915: Introduce a for_each_intel_encoder() macro"
> "drm/i915: lock around link status and link training."
>
> Are you going to apply these? The second one is definitely needed in
> -fixes imo.
I've rebased -fixes on top of 3.17-rc1, so the second patch is there
now. However patch 3 still doesn't apply. Also, if we're going to queue
these for stable to fix 3.16, it's easier if we don't depend on
for_each_intel_encoder. Could you rebase this on -fixes now please?
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-08-18 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 18:52 [PATCH 1/4] drm/i915: fix HPD IRQ reenable work cancelation Imre Deak
2014-08-13 15:11 ` [PATCH v2 1/5] drm/i915: take display port power domain in DP HPD handler Imre Deak
2014-08-13 21:06 ` Dave Airlie
2014-08-13 15:11 ` [PATCH v2 2/5] drm/i915: fix HPD IRQ reenable work cancelation Imre Deak
2014-08-13 15:11 ` [PATCH v2 3/5] drm/i915: cancel hotplug and dig_port work during suspend and unload Imre Deak
2014-08-13 15:11 ` [PATCH v2 4/5] drm/i915: make sure VDD is turned off during system suspend Imre Deak
2014-08-13 15:11 ` [PATCH v2 5/5] drm/i915: don't try to retrain a DP link on an inactive CRTC Imre Deak
2014-08-13 16:33 ` [PATCH 1/4] drm/i915: fix HPD IRQ reenable work cancelation Ville Syrjälä
2014-08-15 9:02 ` Imre Deak
2014-08-15 9:48 ` Jani Nikula
2014-08-15 11:26 ` Imre Deak
2014-08-18 10:33 ` Jani Nikula [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=87bnrinl2o.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.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 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.