From: PRC Automation <prc@list.ti.com>
To: Thorsten Lannynd <t-lannynd@ti.com>
Cc: <meta-arago@lists.yoctoproject.org>, <reatmon@ti.com>,
<detheridge@ti.com>, <b-brnich@ti.com>
Subject: Re: [PATCH v3] meta-arago-disto: chromium: split force-h264-youtube extension into its own package
Date: Wed, 23 Sep 2026 15:15:38 -0500 [thread overview]
Message-ID: <20260923201538.3514930-1-prc@list.ti.com> (raw)
In-Reply-To: <20260923201126.1084567-1-t-lannynd@ti.com>
meta-arago / na / 20260923201126.1084567-1-t-lannynd
PRC Results: FAIL
=========================================================
check-yocto-patches: FAIL
=========================================================
Patches
----------------------------------------
FAIL - [PATCH v3] meta-arago-disto: chromium: split force-h264-youtube extension into its own package
WARN: Missing branches specifier [master/scarthgap/XXXXX]. (META-2)
patch:84
Subject: [PATCH v3] meta-arago-disto: chromium: split force-h264-youtube extension into its own package
ERROR: Commit message too long (> 80 chars): meta-arago-disto: chromium: split force-h264-youtube extension into its own package. (COMMIT-MESSAGE-1)
patch:84
Subject: [PATCH v3] meta-arago-disto: chromium: split force-h264-youtube extension into its own package
For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
next prev parent reply other threads:[~2026-09-23 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 20:11 [PATCH v3] meta-arago-disto: chromium: split force-h264-youtube extension into its own package Thorsten Lannynd
2026-09-23 20:15 ` PRC Automation [this message]
2026-09-23 20:27 ` [meta-arago] " Denys Dmytriyenko
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=20260923201538.3514930-1-prc@list.ti.com \
--to=prc@list.ti.com \
--cc=b-brnich@ti.com \
--cc=detheridge@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=t-lannynd@ti.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.