From: Patchwork <patchwork@patchwork.openembedded.org>
To: Martyn Welch <martyn.welch@collabora.co.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "[v2] package.bbclass: add proh..." and 1 more
Date: Mon, 13 Nov 2017 19:39:31 -0000 [thread overview]
Message-ID: <20171113193931.2786.66302@do.openembedded.org> (raw)
In-Reply-To: <1510600788-27455-1-git-send-email-martyn.welch@collabora.co.uk>
== Series Details ==
Series: "[v2] package.bbclass: add proh..." and 1 more
Revision: 1
URL : https://patchwork.openembedded.org/series/9760/
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 sent to the wrong mailing list or some patches from the series correspond to different mailing lists [test_target_mailing_list]
Suggested fix Send the series again to the correct mailing list (ML)
Suggested ML yocto@yoctoproject.org [http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/]
Patch's path: documentation/ref-manual/ref-classes.xml
* 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 a17f3ec910)
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:[~2017-11-13 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 19:19 [PATCH v2 1/2] package.bbclass: add prohibited-path qa test Martyn Welch
2017-11-13 19:19 ` [PATCH v2 2/2] ref-manual: Add documentation for prohibited-path QA test Martyn Welch
2017-11-13 19:39 ` Patchwork [this message]
2017-11-14 12:47 ` [OE-core] [PATCH v2 1/2] package.bbclass: add prohibited-path qa test Alexander Kanavin
2017-11-14 12:47 ` Alexander Kanavin
2017-11-14 12:54 ` [OE-core] " Alexander Kanavin
2017-11-14 12:54 ` Alexander Kanavin
2017-11-14 13:01 ` [OE-core] " Andreas Oberritter
2017-11-14 13:01 ` Andreas Oberritter
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=20171113193931.2786.66302@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=martyn.welch@collabora.co.uk \
--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.