All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: prc@list.ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [patch][PATCH 1/2] u-boot-bb.org: upgrade 2025.07 -> 2025.10
Date: Tue, 21 Oct 2025 16:08:03 -0400	[thread overview]
Message-ID: <20251021200803.GV3125@denix.org> (raw)
In-Reply-To: <20251021200514.2190304-1-prc@list.ti.com>

On Tue, Oct 21, 2025 at 03:05:14PM -0500, PRC Automation via lists.yoctoproject.org wrote:
> meta-ti / na / 20251021200247.52202-1-denis
> 
> PRC Results: FAIL
> 
> =========================================================
>   check-yocto-patches: FAIL
> =========================================================
> Patches
> ----------------------------------------
> FAIL - [patch][PATCH 1/2] u-boot-bb.org: upgrade 2025.07 -> 2025.10
>     ERROR: Invalid branch specifier: "patch". (META-3)

:facepalm:


>         patch:30
>             Subject: [patch][PATCH 1/2] u-boot-bb.org: upgrade 2025.07 -> 2025.10
>     
>     WARN: Commit message does not include file/recipe name: u-boot-bb.org: upgrade 2025.07 -> 2025.10. (COMMIT-MESSAGE-2)
>         patch
> WARN - [master][PATCH 2/2] linux-bb.org: update to 6.12.43
>     WARN: Commit message does not include file/recipe name: linux-bb.org: update to 6.12.43. (COMMIT-MESSAGE-2)
>         patch
> 
> 
> 


      reply	other threads:[~2025-10-21 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 20:02 [patch][PATCH 1/2] u-boot-bb.org: upgrade 2025.07 -> 2025.10 Denys Dmytriyenko
2025-10-21 20:02 ` [master][PATCH 2/2] linux-bb.org: update to 6.12.43 Denys Dmytriyenko
2025-10-21 20:05 ` [patch][PATCH 1/2] u-boot-bb.org: upgrade 2025.07 -> 2025.10 PRC Automation
2025-10-21 20:08   ` Denys Dmytriyenko [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=20251021200803.GV3125@denix.org \
    --to=denis@denix.org \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=prc@list.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.