From: Jani Nikula <jani.nikula@linux.intel.com>
To: Egor Vorontsov <sdoregor@sdore.me>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Egor Vorontsov <sdoregor@sdore.me>
Subject: Re: ✗ i915.CI.BAT: failure for series starting with [v3,1/2] drm/edid: Implement DisplayID Type IX & X timing blocks parsing
Date: Tue, 15 Apr 2025 12:15:04 +0300 [thread overview]
Message-ID: <87jz7lss4n.fsf@intel.com> (raw)
In-Reply-To: <7e2cb3cdcee84975a439980cb94d93eac14bae11.camel@sdore.me>
On Mon, 14 Apr 2025, Egor Vorontsov <sdoregor@sdore.me> wrote:
> The patchset seems stalled, presumably because of this CI dead end.
>
> Is there anything I can do about this issue, or did the thread just get
> lost? Some are even pinging me directly on the state of this now.
I'm sorry, totally my fault, I dropped the ball.
I resent the patches for fresh results [1], and will merge them via
drm-misc-next.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1744708239.git.jani.nikula@intel.com
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-04-15 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 11:06 [PATCH v3 1/2] drm/edid: Implement DisplayID Type IX & X timing blocks parsing Egor Vorontsov
2025-02-14 11:06 ` [PATCH v3 2/2] drm/edid: Refactor DisplayID timing block structs Egor Vorontsov
2025-02-14 16:05 ` Jani Nikula
2025-02-14 16:04 ` [PATCH v3 1/2] drm/edid: Implement DisplayID Type IX & X timing blocks parsing Jani Nikula
[not found] ` <173955656648.2118687.12350276607296168996@b555e5b46a47>
2025-04-14 19:00 ` ✗ i915.CI.BAT: failure for series starting with [v3,1/2] " Egor Vorontsov
2025-04-15 9:15 ` 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=87jz7lss4n.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sdoregor@sdore.me \
--cc=tzimmermann@suse.de \
/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