public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for kernel-yocto: consolidated pull request
Date: Fri, 26 Jan 2018 14:32:58 -0000	[thread overview]
Message-ID: <20180126143258.15542.64523@do.openembedded.org> (raw)
In-Reply-To: <cover.1516973739.git.bruce.ashfield@windriver.com>

== Series Details ==

Series: kernel-yocto: consolidated pull request
Revision: 1
URL   : https://patchwork.openembedded.org/series/10720/
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 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 8485438140)



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



  parent reply	other threads:[~2018-01-26 14:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 13:59 [PATCH 00/12] kernel-yocto: consolidated pull request Bruce Ashfield
2018-01-26 13:59 ` [PATCH 01/12] linux-yocto/4.9: update to v4.9.71 Bruce Ashfield
2018-01-26 13:59 ` [PATCH 02/12] linux-yocto/4.9: fix aufs build Bruce Ashfield
2018-01-26 13:59 ` [PATCH 03/12] linux-yocto/4.4: update to 4.4.99 Bruce Ashfield
2018-01-26 13:59 ` [PATCH 04/12] linux-yocto/4.12: CQM and rdt backports Bruce Ashfield
2018-01-26 13:59 ` [PATCH 05/12] linux-yocto/4.12: coffeeLake-s graphics and audio support Bruce Ashfield
2018-01-26 13:59 ` [PATCH 06/12] linux-yocto/4.12: drm & mips fixes Bruce Ashfield
2018-01-26 13:59 ` [PATCH 07/12] kernel-yocto: make SRC_URI defconfig removal more specific Bruce Ashfield
2018-01-26 13:59 ` [PATCH 08/12] linux-yocto/4.12: iwlwifi and pci id backports Bruce Ashfield
2018-01-26 13:59 ` [PATCH 09/12] linux-yocto/4.4: update to v4.4.113 Bruce Ashfield
2018-01-26 13:59 ` [PATCH 10/12] linux-yocto/4.9: update to v4.9.78 Bruce Ashfield
2018-01-26 13:59 ` [PATCH 11/12] linux-yocto/4.12: update to v4.12.19 Bruce Ashfield
2018-01-26 13:59 ` [RFC][PATCH 12/12] make-mod-scripts: change how some kernel module tools are built Bruce Ashfield
2018-02-15 20:12   ` Peter Kjellerstedt
2018-02-16 16:16     ` Bruce Ashfield
2018-01-26 14:32 ` Patchwork [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-06 17:35 [PATCH 00/10][v2] kernel-yocto: consolidated pull request bruce.ashfield
2020-02-06 18:02 ` ✗ patchtest: failure for " Patchwork
2020-02-05 23:12 [PATCH 0/9] " bruce.ashfield
2020-02-05 23:32 ` ✗ patchtest: failure for " Patchwork
2018-03-06 18:11 [PATCH 0/9] " Bruce Ashfield
2018-03-06 18:33 ` ✗ patchtest: failure for " Patchwork
2018-02-19  2:25 [PATCH 0/7] " Bruce Ashfield
2018-02-19  3:03 ` ✗ patchtest: failure for " Patchwork
2017-08-21  2:58 [PATCH 0/9] " Bruce Ashfield
2017-08-21  3:05 ` ✗ patchtest: failure for " Patchwork

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=20180126143258.15542.64523@do.openembedded.org \
    --to=patchwork@patchwork.openembedded.org \
    --cc=bruce.ashfield@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