All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org,
	Ville Syrjala <ville.syrjala@linux.intel.com>,
	Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH v4 5/6] drm/probe-helper: use drm_kms_helper_connector_hotplug_event
Date: Wed, 27 Oct 2021 17:24:20 +0200	[thread overview]
Message-ID: <YXlvJIF12cwk8rFo@ravnborg.org> (raw)
In-Reply-To: <20211018084707.32253-6-contact@emersion.fr>

Hi Simon,

On Mon, Oct 18, 2021 at 08:47:30AM +0000, Simon Ser wrote:
> If an hotplug event only updates a single connector, use
> drm_kms_helper_connector_hotplug_event instead of
> drm_kms_helper_hotplug_event.
> 
> Changes in v4:
> - Simplify loop logic (Ville, Sam)
> - Update drm_connector_helper_hpd_irq_event (Maxime)
> 
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Maxime Ripard <maxime@cerno.tech>

Thanks, I like this better.
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>

Maybe I am late and this was already applied...

	Sam

  parent reply	other threads:[~2021-10-27 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  8:47 [PATCH v4 0/6] drm: add per-connector hotplug events Simon Ser
2021-10-18  8:47 ` [PATCH v4 1/6] drm/sysfs: introduce drm_sysfs_connector_hotplug_event Simon Ser
2021-10-18  8:47 ` [PATCH v4 2/6] drm/probe-helper: add drm_kms_helper_connector_hotplug_event Simon Ser
2021-10-18  8:47 ` [PATCH v4 3/6] drm/connector: use drm_sysfs_connector_hotplug_event Simon Ser
2021-10-18  8:47 ` [PATCH v4 4/6] amdgpu: use drm_kms_helper_connector_hotplug_event Simon Ser
2021-10-18  8:47 ` [PATCH v4 5/6] drm/probe-helper: " Simon Ser
2021-10-19 14:04   ` Maxime Ripard
2021-10-27 15:24   ` Sam Ravnborg [this message]
2021-10-18  8:47 ` [PATCH v4 6/6] i915/display/dp: send a more fine-grained link-status uevent Simon Ser
2021-10-28 16:37   ` Ville Syrjälä

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=YXlvJIF12cwk8rFo@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=contact@emersion.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.