From: Patchwork <patchwork@patchwork.openembedded.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Introduce ARC port of OpenEmbedded
Date: Mon, 17 Sep 2018 22:04:00 -0000 [thread overview]
Message-ID: <20180917220400.13840.70015@do.openembedded.org> (raw)
In-Reply-To: <20180917212943.27237-1-abrodkin@synopsys.com>
== Series Details ==
Series: Introduce ARC port of OpenEmbedded
Revision: 1
URL : https://patchwork.openembedded.org/series/14104/
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 Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 6a1e550838)
* Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence]
Suggested fix Sign off the added patch file (meta/recipes-devtools/gcc/gcc-8.2/0041-ARC-fix-spec-gen.patch)
* 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-support/nspr/nspr/0004-Add-ARC-support.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-09-17 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 21:29 [PATCH 00/10] Introduce ARC port of OpenEmbedded Alexey Brodkin
2018-09-17 21:29 ` [PATCH 01/10] siteinfo: Define data for ARC Alexey Brodkin
2018-09-18 23:24 ` Khem Raj
2018-09-17 21:29 ` [PATCH 02/10] site: Add ARC linux Alexey Brodkin
2018-09-17 21:29 ` [PATCH 03/10] kernel-arch.bbclass: Add ARC to kernel arch map Alexey Brodkin
2018-09-17 21:29 ` [PATCH 04/10] openssl: Add support for ARC Alexey Brodkin
2018-09-17 21:29 ` [PATCH 05/10] nspr: Add ARC support Alexey Brodkin
2018-09-17 21:29 ` [PATCH 06/10] libgpg-error: " Alexey Brodkin
2018-09-17 21:29 ` [PATCH 07/10] icu: " Alexey Brodkin
2018-09-17 21:29 ` [PATCH 08/10] gcc: Disable libitm for ARC Alexey Brodkin
2018-09-17 21:29 ` [PATCH 09/10] binutils: Fix Glibc building " Alexey Brodkin
2018-09-17 21:29 ` [PATCH 10/10] gcc: Fix specs generation " Alexey Brodkin
2018-09-18 23:21 ` Khem Raj
2018-09-17 22:04 ` Patchwork [this message]
2018-09-18 23:28 ` [PATCH 00/10] Introduce ARC port of OpenEmbedded Khem Raj
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=20180917220400.13840.70015@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=Alexey.Brodkin@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox