From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, imre.deak@intel.com
Subject: Re: [RFC 0/7] drm/i915: pass encoder around more for port/phy checks
Date: Wed, 20 Mar 2024 17:49:12 +0200 [thread overview]
Message-ID: <87v85gnbt3.fsf@intel.com> (raw)
In-Reply-To: <Zfr94E30khxsVf3G@intel.com>
On Wed, 20 Mar 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> I have basically that same patch sitting in some branch.
I would expect no less. ;D
> With commit messages polished the series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks, fixed up the commit messages and posted v1 for CI.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-03-20 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 14:28 [RFC 0/7] drm/i915: pass encoder around more for port/phy checks Jani Nikula
2024-03-12 14:28 ` [RFC 1/7] drm/hdmi: convert *_port_to_ddc_pin() to *_encoder_to_ddc_pin() Jani Nikula
2024-03-12 14:28 ` [RFC 2/7] drm/i915/ddi: pass encoder to intel_wait_ddi_buf_active() Jani Nikula
2024-03-12 14:28 ` [RFC 3/7] drm/i915/snps: pass encoder to intel_snps_phy_update_psr_power_state() Jani Nikula
2024-03-12 14:28 ` [RFC 4/7] drm/i915/display: add intel_encoder_is_*() and _to_*() functions Jani Nikula
2024-03-12 14:29 ` [RFC 5/7] drm/i915/display: use intel_encoder_is/to_* functions Jani Nikula
2024-03-12 14:29 ` [RFC 6/7] drm/i915/cx0: remove intel_is_c10phy() Jani Nikula
2024-03-12 14:29 ` [RFC 7/7] drm/i915/cx0: pass encoder instead of i915 and port around Jani Nikula
2024-03-12 17:35 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: pass encoder around more for port/phy checks Patchwork
2024-03-12 17:35 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-03-12 17:54 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-03-20 15:16 ` [RFC 0/7] " Ville Syrjälä
2024-03-20 15:49 ` Jani Nikula [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=87v85gnbt3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox