From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] drm/i915: Reordered AUX patches from type safety series
Date: Mon, 16 Nov 2015 16:22:35 +0200 [thread overview]
Message-ID: <20151116142235.GN4437@intel.com> (raw)
In-Reply-To: <87h9krh83c.fsf@intel.com>
On Thu, Nov 12, 2015 at 11:37:11AM +0200, Jani Nikula wrote:
> On Wed, 11 Nov 2015, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Chris requested that I try to reorder the DP AUX patches in the last
> > register type safety series [1] to form a better story. Here is the
> > result. The final code is exactly the same as before (apart from the
> > kasprintf() changes), so I kept the previous r-b's in place, with
> > some added version annotations.
>
> I reviewed the one patch that was missing r-b, and eyeballed the ones
> with previous r-b's a bit, and it all looks good to go.
Thanks for the reviews. Series pushed to dinq.
>
> BR,
> Jani.
>
>
> >
> > [1] http://lists.freedesktop.org/archives/intel-gfx/2015-November/079453.html
> >
> > Ville Syrjälä (7):
> > drm/i915: Replace aux_ch_ctl_reg check with port check
> > drm/i915: Replace the aux ddc name switch statement with kasprintf()
> > drm/i915: Parametrize AUX registers
> > drm/i915: Remove the magic AUX_CTL is at DP + foo tricks
> > drm/i915: Store aux data reg offsets in intel_dp->aux_ch_data_reg[]
> > drm/i915: Add dev_priv->psr_mmio_base
> > drm/i915: Model PSR AUX register selection more like the normal AUX
> > code
> >
> > drivers/gpu/drm/i915/i915_debugfs.c | 4 +-
> > drivers/gpu/drm/i915/i915_drv.h | 2 +
> > drivers/gpu/drm/i915/i915_reg.h | 115 ++++++++-------
> > drivers/gpu/drm/i915/intel_dp.c | 282 +++++++++++++++++++++++++-----------
> > drivers/gpu/drm/i915/intel_drv.h | 1 +
> > drivers/gpu/drm/i915/intel_psr.c | 51 +++++--
> > 6 files changed, 298 insertions(+), 157 deletions(-)
>
> --
> Jani Nikula, Intel Open Source Technology Center
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-11-16 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 18:34 [PATCH 0/7] drm/i915: Reordered AUX patches from type safety series ville.syrjala
2015-11-11 18:34 ` [PATCH 1/7] drm/i915: Replace aux_ch_ctl_reg check with port check ville.syrjala
2015-11-11 18:34 ` [PATCH 2/7] drm/i915: Replace the aux ddc name switch statement with kasprintf() ville.syrjala
2015-11-12 9:23 ` Jani Nikula
2015-11-11 18:34 ` [PATCH 3/7] drm/i915: Parametrize AUX registers ville.syrjala
2015-11-11 18:34 ` [PATCH 4/7] drm/i915: Remove the magic AUX_CTL is at DP + foo tricks ville.syrjala
2015-11-11 18:34 ` [PATCH 5/7] drm/i915: Store aux data reg offsets in intel_dp->aux_ch_data_reg[] ville.syrjala
2015-11-11 18:34 ` [PATCH 6/7] drm/i915: Add dev_priv->psr_mmio_base ville.syrjala
2015-11-11 18:34 ` [PATCH 7/7] drm/i915: Model PSR AUX register selection more like the normal AUX code ville.syrjala
2015-11-12 9:37 ` [PATCH 0/7] drm/i915: Reordered AUX patches from type safety series Jani Nikula
2015-11-16 14:22 ` Ville Syrjälä [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=20151116142235.GN4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox