From: Greg KH <gregkh@linuxfoundation.org>
To: Lyude <cpaul@redhat.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Backported vlv fixes for 4.7.y
Date: Mon, 22 Aug 2016 16:33:32 -0400 [thread overview]
Message-ID: <20160822203332.GA5030@kroah.com> (raw)
In-Reply-To: <1471879896-19761-1-git-send-email-cpaul@redhat.com>
On Mon, Aug 22, 2016 at 11:31:31AM -0400, Lyude wrote:
> Hope this didn't take too long! Here's the backported versions of the patches
> you had trouble applying to stable. The patch for FBC won't be necessary as
> that is already present in 4.7.y.
>
> Cheers,
> Lyude
Thanks, but what are the git commit ids of these patches in Linus's
tree? I need those to add to the commits...
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Lyude <cpaul@redhat.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 0/4] Backported vlv fixes for 4.7.y
Date: Mon, 22 Aug 2016 16:33:32 -0400 [thread overview]
Message-ID: <20160822203332.GA5030@kroah.com> (raw)
In-Reply-To: <1471879896-19761-1-git-send-email-cpaul@redhat.com>
On Mon, Aug 22, 2016 at 11:31:31AM -0400, Lyude wrote:
> Hope this didn't take too long! Here's the backported versions of the patches
> you had trouble applying to stable. The patch for FBC won't be necessary as
> that is already present in 4.7.y.
>
> Cheers,
> Lyude
Thanks, but what are the git commit ids of these patches in Linus's
tree? I need those to add to the commits...
thanks,
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-22 20:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 11:47 FAILED: patch "[PATCH] drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug()" failed to apply to 4.7-stable tree gregkh
2016-08-22 15:31 ` [PATCH 0/4] Backported vlv fixes for 4.7.y Lyude
2016-08-22 15:31 ` Lyude
2016-08-22 15:31 ` [PATCH 1/4] drm/i915/vlv: Make intel_crt_reset() per-encoder Lyude
2016-08-22 15:31 ` Lyude
2016-08-22 15:31 ` [PATCH 2/4] drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init() Lyude
2016-08-22 15:31 ` Lyude
2016-08-22 15:31 ` [PATCH 3/4] drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug() Lyude
2016-08-22 15:31 ` Lyude
2016-08-22 15:31 ` [PATCH 4/4] drm/i915: Enable polling when we don't have hpd Lyude
2016-08-22 15:31 ` Lyude
2016-08-22 20:33 ` Greg KH [this message]
2016-08-22 20:33 ` [PATCH 0/4] Backported vlv fixes for 4.7.y Greg KH
2016-08-29 21:27 ` Lyude Paul
2016-08-29 21:27 ` Lyude Paul
2016-09-05 13:01 ` Greg KH
2016-09-05 13:01 ` Greg KH
2016-08-22 15:40 ` ✗ Ro.CI.BAT: failure for series starting with [1/4] drm/i915/vlv: Make intel_crt_reset() per-encoder Patchwork
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=20160822203332.GA5030@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=cpaul@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.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.