From: Patchwork <patchwork@patchwork.openembedded.org>
To: leimaohui <leimaohui@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for openssl: Fix a build bug on aarch64BE. (rev4)
Date: Mon, 17 Jun 2019 04:00:43 -0000 [thread overview]
Message-ID: <20190617040043.2330.39259@do> (raw)
In-Reply-To: <1559771208-32780-1-git-send-email-leimaohui@cn.fujitsu.com>
== Series Details ==
Series: openssl: Fix a build bug on aarch64BE. (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/18134/
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-connectivity/openssl/openssl/0001-Fix-build-error-for-aarch64-big-endian.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:[~2019-06-17 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 21:46 [PATCH v2] openssl: Fix a build bug on aarch64BE Lei Maohui
2019-06-17 4:00 ` Patchwork [this message]
2019-06-17 5:16 ` ChenQi
2019-06-18 7:58 ` Lei, Maohui
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=20190617040043.2330.39259@do \
--to=patchwork@patchwork.openembedded.org \
--cc=leimaohui@cn.fujitsu.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.