From: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libseccomp: upgrade 2.6.0 -> 2.6.1
Date: Thu, 23 Jul 2026 08:02:14 -0700 [thread overview]
Message-ID: <1009290.1784818934825857798@lists.openembedded.org> (raw)
In-Reply-To: <20260723141839.13175-1-jaipaul.cheernam@est.tech>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
Hi,
This is a false positive. The @v3 flagged by patchtest is from a verbatim upstream git log entry:
8e31cd254be3 github: bump codeql version to @v3
It refers to a GitHub Actions version tag (actions/codeql-action@v3), not a GitHub username mention.
I'd prefer to keep the upstream log intact rather than modify it.
Happy to resend with the @ stripped if maintainers prefer, but wanted to flag this as a patchtest false positive that might be worth addressing in the test itself.
Thanks,
Jaipaul
[-- Attachment #2: Type: text/html, Size: 2327 bytes --]
next prev parent reply other threads:[~2026-07-23 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 14:18 [PATCH] libseccomp: upgrade 2.6.0 -> 2.6.1 Jaipaul Cheernam
2026-07-23 14:31 ` Patchtest results for " patchtest
2026-07-23 14:58 ` Jaipaul Cheernam
2026-07-23 15:02 ` [OE-core] " Quentin Schulz
2026-07-23 15:02 ` Jaipaul Cheernam [this message]
2026-07-23 15:31 ` [PATCH v2] " Jaipaul Cheernam
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=1009290.1784818934825857798@lists.openembedded.org \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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