mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: dri-devel@lists.freedesktop.org,
	 Helen Koike <helen.koike@collabora.com>
Cc: robdclark@gmail.com, linux-arm-msm@vger.kernel.org,
	 neil.armstrong@linaro.org, linux-amlogic@lists.infradead.org,
	 p.zabel@pengutronix.de, linux-mediatek@lists.infradead.org,
	heiko@sntech.de,  jani.nikula@linux.intel.com,
	intel-gfx@lists.freedesktop.org,  alexander.deucher@amd.com,
	amd-gfx@lists.freedesktop.org,  airlied@redhat.com,
	daniel@ffwll.ch, michel.daenzer@mailbox.org,
	 daniel@fooishbar.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: drm/ci: add entries for xfail files
Date: Thu, 26 Oct 2023 17:34:08 +0200	[thread overview]
Message-ID: <169833444817.1001410.15120310571741480170.b4-ty@kernel.org> (raw)
In-Reply-To: <20230919182249.153499-1-helen.koike@collabora.com>

On Tue, 19 Sep 2023 15:22:49 -0300, Helen Koike wrote:
> DRM CI keeps track of which tests are failing, flaking or being skipped
> by the ci in the expectations files. Add entries for those files to the
> corresponding driver maintainer, so they can be notified when they
> change.
> 
> 

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2023-10-26 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 18:22 Helen Koike
2023-09-20  6:13 ` Maxime Ripard
2023-10-02  7:00 ` neil.armstrong
2023-10-26 15:34 ` Maxime Ripard [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=169833444817.1001410.15120310571741480170.b4-ty@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=helen.koike@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=michel.daenzer@mailbox.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robdclark@gmail.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
all inboxes | Powered by JetHome®