From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/i915/dp: aux and dpcd fixes
Date: Mon, 23 Sep 2013 09:30:31 +0200 [thread overview]
Message-ID: <20130923073031.GZ32145@phenom.ffwll.local> (raw)
In-Reply-To: <87siww5b8w.fsf@intel.com>
On Mon, Sep 23, 2013 at 08:59:43AM +0300, Jani Nikula wrote:
> On Fri, 20 Sep 2013, Jani Nikula <jani.nikula@intel.com> wrote:
> > I haven't received confirmation from various bug reporters whether these
> > actually fix any issues, but here goes anyway.
>
> These are on the series, but I bet it's patch 2/4 that does the trick.
>
> Reference: https://bugs.freedesktop.org/show_bug.cgi?id=60263
> Tested-by: Nicolas Suzor <nic@suzor.com>
I've picked up patch 2 from this series for -fixes, 4 for dinq (the other
two lack r-bs).
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-09-23 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:42 [PATCH 0/4] drm/i915/dp: aux and dpcd fixes Jani Nikula
2013-09-20 13:42 ` [PATCH 1/4] drm/i915/dp: retry i2c-over-aux seven times on AUX DEFER Jani Nikula
2013-09-20 20:38 ` Todd Previte
2013-09-24 6:39 ` Jani Nikula
2013-09-27 11:51 ` Jani Nikula
2013-09-27 19:07 ` Todd Previte
2013-09-27 19:59 ` Daniel Vetter
2013-09-20 13:42 ` [PATCH 2/4] drm/i915/dp: increase i2c-over-aux retry interval " Jani Nikula
2013-09-20 20:56 ` Todd Previte
2013-09-20 21:53 ` Daniel Vetter
2013-09-20 13:42 ` [PATCH 3/4] drm/i915/dp: downstream port capabilities are not present in DPCD 1.0 Jani Nikula
2013-09-20 13:42 ` [PATCH 4/4] drm/i915/dp: read DPCD PSR capability only on eDP Jani Nikula
2013-09-20 20:50 ` Todd Previte
2013-09-20 20:57 ` Paulo Zanoni
2013-09-20 22:31 ` Todd Previte
2013-09-23 7:29 ` Daniel Vetter
2013-09-23 5:59 ` [PATCH 0/4] drm/i915/dp: aux and dpcd fixes Jani Nikula
2013-09-23 7:30 ` Daniel Vetter [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=20130923073031.GZ32145@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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