From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/14] drm/i915: Pass intel_atomic_state to cdclk funcs
Date: Tue, 4 Jun 2019 16:45:49 +0300 [thread overview]
Message-ID: <20190604134549.GF5942@intel.com> (raw)
In-Reply-To: <20190517193132.8140-1-ville.syrjala@linux.intel.com>
On Fri, May 17, 2019 at 10:31:19PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Pass around intel_atomic_state rather than drm_atomic_state.
> This avoids some extra casts and annoing aliasing variables.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
Series pushed with Maarten's irc rb. Thanks.
21:41 < vsyrjala> anyone want to review a new paintjob? https://patchwork.freedesktop.org/series/60803/
22:18 < mlankhorst_> vsyrjala: irc r-b?
22:18 < mlankhorst_> nice cleanup
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-06-04 13:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 19:31 [PATCH 01/14] drm/i915: Pass intel_atomic_state to cdclk funcs Ville Syrjala
2019-05-17 19:31 ` [PATCH 02/14] drm/i915: Clean up cdclk vfunc assignments Ville Syrjala
2019-05-17 19:31 ` [PATCH 03/14] drm/i915: Pass intel_atomic state to check_digital_port_conflicts() Ville Syrjala
2019-05-17 19:31 ` [PATCH 04/14] drm/i915: Use intel_ types in intel_modeset_clear_plls() Ville Syrjala
2019-05-17 19:31 ` [PATCH 05/14] drm/i915: Use intel_ types in haswell_mode_set_planes_workaround() Ville Syrjala
2019-05-17 19:31 ` [PATCH 06/14] drm/i915: Don't pass the crtc to intel_dump_pipe_config() Ville Syrjala
2019-05-17 19:31 ` [PATCH 07/14] drm/i915: Don't pass the crtc to intel_modeset_pipe_config() Ville Syrjala
2019-05-17 19:31 ` [PATCH 08/14] drm/i915: Use intel_ types in intel_modeset_checks() Ville Syrjala
2019-05-17 19:31 ` [PATCH 09/14] drm/i915: Use intel_ types in intel_atomic_check() Ville Syrjala
2019-05-17 19:31 ` [PATCH 10/14] drm/i915: Move state dump to the end of atomic_check() Ville Syrjala
2019-05-17 19:31 ` [PATCH 11/14] drm/i915: Include crtc_state.active in crtc state dumps Ville Syrjala
2019-05-17 19:31 ` [PATCH 12/14] drm/i915: Dump failed crtc states during atomic check Ville Syrjala
2019-05-17 19:31 ` [PATCH 13/14] drm/i915: Make state dumpers take a const state Ville Syrjala
2019-05-17 19:31 ` [PATCH 14/14] drm/i915: Fix plane state dumps Ville Syrjala
2019-05-17 19:57 ` ✗ Fi.CI.SPARSE: warning for series starting with [01/14] drm/i915: Pass intel_atomic_state to cdclk funcs Patchwork
2019-05-17 20:12 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-18 10:33 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-04 13:45 ` 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=20190604134549.GF5942@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).