From: Jani Nikula <jani.nikula@intel.com>
To: neil.armstrong@linaro.org, dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: Re: [PATCH 0/2] drm/bridge: start moving towards struct drm_edid
Date: Wed, 03 Jan 2024 12:13:45 +0200 [thread overview]
Message-ID: <87a5pm2086.fsf@intel.com> (raw)
In-Reply-To: <87edfes07x.fsf@intel.com>
On Fri, 22 Dec 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> Okay, I rebased and pushed [1]. Probably doesn't make sense to send a
> patch bomb like that right now...
And here are the patches:
https://patchwork.freedesktop.org/series/128149/
BR,
Jani.
>
> BR,
> Jani.
>
>
> [1] https://gitlab.freedesktop.org/jani/linux/-/commits/drm-edid-bridge
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-01-03 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:39 [PATCH 0/2] drm/bridge: start moving towards struct drm_edid Jani Nikula
2023-10-26 9:39 ` [PATCH 1/2] drm/bridge: add ->edid_read hook and drm_bridge_edid_read() Jani Nikula
2023-12-22 19:27 ` Dmitry Baryshkov
2023-12-27 11:45 ` Jani Nikula
2023-10-26 9:39 ` [PATCH 2/2] drm/bridge: switch to drm_bridge_read_edid() Jani Nikula
2023-11-14 11:53 ` [PATCH 0/2] drm/bridge: start moving towards struct drm_edid Jani Nikula
2023-12-19 12:15 ` Jani Nikula
2023-12-22 8:09 ` Neil Armstrong
2023-12-22 9:24 ` Jani Nikula
2023-12-22 15:53 ` Jani Nikula
2024-01-03 10:13 ` 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=87a5pm2086.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.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 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.