From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for bluez5: Fix ptest hang
Date: Fri, 24 Aug 2018 14:35:18 +0800 [thread overview]
Message-ID: <5B7FA726.2020102@windriver.com> (raw)
In-Reply-To: <20180824063300.13842.33781@do.openembedded.org>
Will resend V2 to update the typo from Upsteam-Status to Upstream-Status.
Thanks,
On 2018年08月24日 14:33, Patchwork wrote:
> == Series Details ==
>
> Series: bluez5: Fix ptest hang
> Revision: 1
> URL : https://patchwork.openembedded.org/series/13703/
> 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/bluez5/bluez5/0001-test-gatt-Fix-hung-issue.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
>
>
prev parent reply other threads:[~2018-08-24 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 6:07 [PATCH] bluez5: Fix ptest hang mingli.yu
2018-08-24 6:33 ` ✗ patchtest: failure for " Patchwork
2018-08-24 6:35 ` Yu, Mingli [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=5B7FA726.2020102@windriver.com \
--to=mingli.yu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox