Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: swee.aun.khor@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Support combination of MUSL and x32 build
Date: Thu, 06 Jul 2017 07:31:21 -0000	[thread overview]
Message-ID: <20170706073121.2380.80731@do.openembedded.org> (raw)
In-Reply-To: <cover.1499127835.git.swee.aun.khor@intel.com>

== Series Details ==

Series: Support combination of MUSL and x32 build
Revision: 1
URL   : https://patchwork.openembedded.org/series/7591/
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-support/libffi/libffi/0001-libffi-Support-musl-x32-build.patch (possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)



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-07-06  7:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 23:56 [PATCH 0/7] Support combination of MUSL and x32 build swee.aun.khor
2017-07-05 23:56 ` [PATCH 1/7] insane.bbclass: Support musl-x32 swee.aun.khor
2017-07-05 23:56 ` [PATCH 2/7] siteinfo.bbclass: " swee.aun.khor
2017-07-05 23:56 ` [PATCH 3/7] gnu-efi: Support musl-x32 build swee.aun.khor
2017-07-05 23:56 ` [PATCH 4/7] grub-efi: Support musl-x32 swee.aun.khor
2017-07-05 23:56 ` [PATCH 5/7] openssl: Support musl-x32 build swee.aun.khor
2017-07-06  7:23   ` Khem Raj
2017-07-06  9:15     ` Khor, Swee Aun
2017-07-05 23:56 ` [PATCH 6/7] perl: " swee.aun.khor
2017-07-05 23:56 ` [PATCH 7/7] libffi: " swee.aun.khor
2017-07-06  7:22   ` Khem Raj
2017-07-06  8:25     ` Khor, Swee Aun
2017-07-06 14:51   ` Wold, Saul
2017-07-06 23:22     ` Khor, Swee Aun
2017-07-06  7:31 ` 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=20170706073121.2380.80731@do.openembedded.org \
    --to=patchwork@patchwork.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=swee.aun.khor@intel.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