From: Patchwork <patchwork@patchwork.openembedded.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for kernel-yocto: consolidated pull request
Date: Tue, 06 Mar 2018 18:33:04 -0000 [thread overview]
Message-ID: <20180306183304.15539.42859@do.openembedded.org> (raw)
In-Reply-To: <cover.1520359364.git.bruce.ashfield@windriver.com>
== Series Details ==
Series: kernel-yocto: consolidated pull request
Revision: 1
URL : https://patchwork.openembedded.org/series/11278/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:
* Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format]
Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
Standard format Upstream-Status: <Valid status>
Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]
If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
next prev parent reply other threads:[~2018-03-06 18:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 18:11 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2018-03-06 18:11 ` [PATCH 1/9 v3] kernel-devsrc: restructure for out of tree (and on target) module builds Bruce Ashfield
2018-03-07 8:40 ` Burton, Ross
2018-03-07 13:35 ` Bruce Ashfield
2018-03-08 18:51 ` Richard Purdie
2018-03-15 13:45 ` Bruce Ashfield
2018-03-29 13:30 ` Richard Purdie
2018-03-06 18:11 ` [PATCH 2/9] linux-libc-headers: update to 4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 3/9] linux-yocto/4.15: update to v4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 4/9] linux-yocto/4.14: update to v4.14.24 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 5/9] linux-yocto/4.12: fix aufs compile warning Bruce Ashfield
2018-03-06 18:11 ` [PATCH 6/9] linux-yocto/4.12: memleak and build warning fixes Bruce Ashfield
2018-03-06 18:11 ` [PATCH 7/9] linux-yocto: aufs and systemtap Bruce Ashfield
2018-03-07 8:38 ` Burton, Ross
2018-03-07 13:39 ` Bruce Ashfield
2018-03-07 15:06 ` Bruce Ashfield
2018-03-07 15:35 ` Burton, Ross
2018-03-14 12:41 ` Burton, Ross
2018-03-14 12:46 ` Bruce Ashfield
2018-03-14 12:50 ` Burton, Ross
2018-03-14 15:11 ` Bruce Ashfield
2018-03-06 18:11 ` [PATCH 8/9] linux-yocto/4.12: warning: drm/i915/cfl: Coffee Lake works on Kaby Lake PCH Bruce Ashfield
2018-03-06 18:11 ` [PATCH 9/9] kernel: make copying of crtsavres.o conditional Bruce Ashfield
2018-03-06 18:33 ` Patchwork [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 17:35 [PATCH 00/10][v2] kernel-yocto: consolidated pull request bruce.ashfield
2020-02-06 18:02 ` ✗ patchtest: failure for " Patchwork
2020-02-05 23:12 [PATCH 0/9] " bruce.ashfield
2020-02-05 23:32 ` ✗ patchtest: failure for " Patchwork
2018-02-19 2:25 [PATCH 0/7] " Bruce Ashfield
2018-02-19 3:03 ` ✗ patchtest: failure for " Patchwork
2018-01-26 13:59 [PATCH 00/12] " Bruce Ashfield
2018-01-26 14:32 ` ✗ patchtest: failure for " Patchwork
2017-08-21 2:58 [PATCH 0/9] " Bruce Ashfield
2017-08-21 3:05 ` ✗ patchtest: failure for " Patchwork
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=20180306183304.15539.42859@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=bruce.ashfield@windriver.com \
--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 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.