Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Misc recipe fixes and updates
Date: Mon, 12 Jun 2017 15:01:49 -0000	[thread overview]
Message-ID: <20170612150149.1042.86315@do.openembedded.org> (raw)
In-Reply-To: <cover.1497279306.git.raj.khem@gmail.com>

== Series Details ==

Series: Misc recipe fixes and updates
Revision: 1
URL   : https://patchwork.openembedded.org/series/7197/
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] 
  Suggested fix    Add Upstream-Status: <status> to the header of meta/recipes-core/ovmf/ovmf/no-stack-protector-all-archs.patch (possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)

* 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 aea90e9ee6)

* 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-core/ovmf/ovmf/no-stack-protector-all-archs.patch)



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] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe



      parent reply	other threads:[~2017-06-12 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 14:58 [PATCH 0/7] Misc recipe fixes and updates Khem Raj
2017-06-12 14:59 ` [PATCH 1/7] mpg123: Upgrade to 1.25.0 Khem Raj
2017-06-12 14:59 ` [PATCH 2/7] binutils-2.28: Update to latest on release branch Khem Raj
2017-06-12 14:59 ` [PATCH 3/7] ltp: Include stdint.h for uintptr_t Khem Raj
2017-06-12 14:59 ` [PATCH 4/7] libnsl2: Include stdint.h Khem Raj
2017-06-12 14:59 ` [PATCH 5/7] valgrind: Fix ptest build with musl Khem Raj
2017-06-12 14:59 ` [PATCH 6/7] kexec-tools: Pass -no-pie to linker Khem Raj
2017-06-12 14:59 ` [PATCH 7/7] ovmf: Update to latest Khem Raj
2017-06-13 16:43   ` Burton, Ross
2017-06-13 17:10     ` Khem Raj
2017-06-13 17:14       ` Khem Raj
2017-06-19 10:42   ` Jussi Kukkonen
2017-06-19 13:44     ` Burton, Ross
2017-06-12 15:01 ` Patchwork [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=20170612150149.1042.86315@do.openembedded.org \
    --to=patchwork@patchwork.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox