From: Stefan Agner <stefan@agner.ch>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for zram: properly implement systemd service
Date: Sun, 06 Oct 2019 00:20:38 +0200 [thread overview]
Message-ID: <a35970e05f8d82a43f3f6aa81052bce2@agner.ch> (raw)
In-Reply-To: <20191005213159.2334.53447@do>
Hi all,
As an on and off contributor I rely on the instructions in the OE wiki.
Unfortunately the example for meta-oe is just next of an example using
the openembedded-core@lists.openembedded.org. Maybe the second example
should contain the correct address for meta-oe as well?
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_patches
--
Stefan
On 2019-10-05 23:31, Patchwork wrote:
> == Series Details ==
>
> Series: zram: properly implement systemd service
> Revision: 1
> URL : https://patchwork.openembedded.org/series/20315/
> 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 openembedded-devel@lists.openembedded.org
> [http://git.openembedded.org/meta-openembedded/]
> Patch's path: meta-oe/recipes-extended/zram/zram/dev-zram0.swap
>
> * 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 520c6f30cd)
>
>
>
> 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-10-05 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 21:08 [PATCH] zram: properly implement systemd service Stefan Agner
2019-10-05 21:31 ` ✗ patchtest: failure for " Patchwork
2019-10-05 22:20 ` Stefan Agner [this message]
2019-10-07 11:41 ` Ross Burton
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=a35970e05f8d82a43f3f6aa81052bce2@agner.ch \
--to=stefan@agner.ch \
--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