From: Jani Nikula <jani.nikula@intel.com>
To: stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Daniel Drake <drake@endlessm.com>,
ville.syrjala@linux.intel.com,
Jim Bride <jim.bride@linux.intel.com>
Subject: v4.9+ stable backport request
Date: Fri, 26 May 2017 14:21:10 +0300 [thread overview]
Message-ID: <87bmqfn9sp.fsf@intel.com> (raw)
Stable team, please backport upstream commits
665788572c64 ("drm/i915/vbt: don't propagate errors from intel_bios_init()")
bb1d132935c2 ("drm/i915/vbt: split out defaults that are set when there is no VBT")
to stable kernels v4.9+. The first is a small refactor that makes the
actual fix in second easier and apply cleanly.
References: http://mid.mail-archive.com/CAD8Lp45zcVDAAshmiBbi3VZ-Zk=bCSBwP0Qw0QL8ibnDO-CECQ@mail.gmail.com
Fixes: 0ce140d45a83 ("drm/i915: Clean up DDI DDC/AUX CH sanitation")
Tested-by: Daniel Drake <drake@endlessm.com>
Cc: <stable@vger.kernel.org> # v4.9+
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Daniel Drake <drake@endlessm.com>,
ville.syrjala@linux.intel.com,
Jim Bride <jim.bride@linux.intel.com>
Cc: Daniel Vetter <daniel@ffwll.ch>
Subject: v4.9+ stable backport request
Date: Fri, 26 May 2017 14:21:10 +0300 [thread overview]
Message-ID: <87bmqfn9sp.fsf@intel.com> (raw)
Stable team, please backport upstream commits
665788572c64 ("drm/i915/vbt: don't propagate errors from intel_bios_init()")
bb1d132935c2 ("drm/i915/vbt: split out defaults that are set when there is no VBT")
to stable kernels v4.9+. The first is a small refactor that makes the
actual fix in second easier and apply cleanly.
References: http://mid.mail-archive.com/CAD8Lp45zcVDAAshmiBbi3VZ-Zk=bCSBwP0Qw0QL8ibnDO-CECQ@mail.gmail.com
Fixes: 0ce140d45a83 ("drm/i915: Clean up DDI DDC/AUX CH sanitation")
Tested-by: Daniel Drake <drake@endlessm.com>
Cc: <stable@vger.kernel.org> # v4.9+
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next reply other threads:[~2017-05-26 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 11:21 Jani Nikula [this message]
2017-05-26 11:21 ` v4.9+ stable backport request Jani Nikula
2017-06-12 13:19 ` Greg KH
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=87bmqfn9sp.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=drake@endlessm.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jim.bride@linux.intel.com \
--cc=stable@vger.kernel.org \
--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 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.