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: native aux read return value fixes and cleanup
Date: Thu, 30 Jan 2014 10:50:22 +0100 [thread overview]
Message-ID: <20140130095022.GN17001@phenom.ffwll.local> (raw)
In-Reply-To: <cover.1391074436.git.jani.nikula@intel.com>
On Thu, Jan 30, 2014 at 11:37:00AM +0200, Jani Nikula wrote:
> Fix and cleanup the rather confused native aux read return values and
> return value checks. Maybe we'll get them right from now on. Just maybe.
>
> Did not have a chance to test this, I'm afraid, but it's pretty
> straightforward.
How does this fit in with Thierry's dp aux helper improvements? I prefer
if we start to converge on that sooner than later ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-01-30 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 9:37 [PATCH 0/4] drm/i915/dp: native aux read return value fixes and cleanup Jani Nikula
2014-01-30 9:37 ` [PATCH 1/4] drm/i915/dp: make intel_dp_aux_native_read() return bool Jani Nikula
2014-01-30 10:07 ` Chris Wilson
2014-01-30 12:00 ` [PATCH v2] " Jani Nikula
2014-01-30 9:37 ` [PATCH 2/4] drm/i915/dp: move intel_dp_aux_native_read_retry() near other reads Jani Nikula
2014-01-30 12:00 ` [PATCH v2] " Jani Nikula
2014-01-30 9:37 ` [PATCH 3/4] drm/i915/dp: clean up cargo culted intel_dp_aux_native_read_retry() usage Jani Nikula
2014-01-30 9:37 ` [PATCH 4/4] drm/i915/dp: fix intel_dp_aux_native_read_retry() return value check Jani Nikula
2014-01-30 9:50 ` Daniel Vetter [this message]
2014-01-30 13:37 ` [PATCH 0/4] drm/i915/dp: native aux read return value fixes and cleanup Jani Nikula
2014-01-30 15:05 ` Jani Nikula
2014-01-30 15:12 ` Daniel Vetter
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=20140130095022.GN17001@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