From: Fritz Koenig <frkoenig@chromium.org>
To: linux-media@vger.kernel.org
Cc: Fritz Koenig <frkoenig@chromium.org>
Subject: Re: [v2] Documentation: media: Fix v4l2_vp9_segmentation
Date: Tue, 24 Mar 2026 16:06:04 -0700 [thread overview]
Message-ID: <CAMfZQbwFwu4q-06eCqhmW-AGaPYFTFmjA5wcA5Yr7MbrLfTaRw@mail.gmail.com> (raw)
In-Reply-To: <69c30f82.050a0220.1ae388.4e92@mx.google.com>
On Tue, Mar 24, 2026 at 3:26 PM Patchwork Integration
<patchwork@media-ci.org> wrote:
>
> Dear Fritz Koenig:
>
> Thanks for your patches! Unfortunately the Media CI robot detected some
> issues:
>
>
>
> Please fix your series, and upload a new version. If you have a patchwork
> account, do not forget to mark the current series as Superseded.
>
> For more details, check the full report at:
> https://linux-media.pages.freedesktop.org/-/users/patchwork/-/jobs/96051061/artifacts/report.htm .
>
>
>
> Best regards, and Happy Hacking!
> Media CI robot on behalf of the linux-media community.
>
> ---
> Check the latest rules for contributing your patches at:
> https://docs.kernel.org/driver-api/media/maintainer-entry-profile.html
>
> If you believe that the CI is wrong, kindly open an issue at
> https://gitlab.freedesktop.org/linux-media/media-ci/-/issues or reply-all
> to this message.
>
This looks like a CI issue:
ERROR: Failed to remove container
3af6cab3e8515aa18b263a8011d0cddb070fa9fc24f018d3f89d5c6b0cc1b885
ERROR: Failed to remove container
bc3a1a2eae3b22087dcb8f5720f1a7dbbe3d1529205915f5b6f410af8b8dcd2c
ERROR: Failed to cleanup volumes
prev parent reply other threads:[~2026-03-24 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 21:00 [PATCH v2] Documentation: media: Fix v4l2_vp9_segmentation Fritz Koenig
[not found] ` <69c30f82.050a0220.1ae388.4e92@mx.google.com>
2026-03-24 23:06 ` Fritz Koenig [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=CAMfZQbwFwu4q-06eCqhmW-AGaPYFTFmjA5wcA5Yr7MbrLfTaRw@mail.gmail.com \
--to=frkoenig@chromium.org \
--cc=linux-media@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox