public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	daniela.plascencia@linux.intel.com,
	richard.purdie@linuxfoundation.org,
	 paul.eggleton@linux.intel.com, joshua.g.lock@intel.com,
	sgw@linux.intel.com, benjamin.esquivel@linux.intel.com
Subject: Re: ✗ patchtest: failure for u-boot: mkimage: fix build
Date: Fri, 4 Nov 2016 10:30:57 -0600	[thread overview]
Message-ID: <602d414e-b507-c4c8-d5d1-50a1e48df05c@linux.intel.com> (raw)
In-Reply-To: <20161104112557.2206.15124@do.openembedded.org>

This is another false positive that has been fixed. Submitted is a valid 
status.


On 11/04/2016 05:25 AM, Patchwork wrote:
> == Series Details ==
>
> Series: u-boot: mkimage: fix build
> URL   : https://patchwork.openembedded.org/series/3768/
> State : failure
>
> == Summary ==
>
> Thank you for your patch submission of the following patch series to OpenEmbedded Core-.
> this is an automated response. Several tests have been executed on the proposed
> series (series 3768, revision 1) by patchtest and the following have failed:
>
>
> Test Name        test_upstream_status_format
> Proposed Fix     Fix Upstream-Status format
> Required format  Upstream-Status: <status>
> Possible Status  Pending, Accepted, Backport, Denied, Inappropriate
> Line             Upstream-Status: Submitted
> Column           18
>
>
> 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] -> ...).
>
> ---
> 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:[~2016-11-04 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:06 [PATCH] u-boot: mkimage: fix build Stefan Müller-Klieser
     [not found] ` <20161104112557.2206.15124@do.openembedded.org>
2016-11-04 16:30   ` Leonardo Sandoval [this message]
2016-11-07 15:00 ` Burton, Ross
2016-11-10 10:01   ` Stefan Müller-Klieser

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=602d414e-b507-c4c8-d5d1-50a1e48df05c@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=benjamin.esquivel@linux.intel.com \
    --cc=daniela.plascencia@linux.intel.com \
    --cc=joshua.g.lock@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sgw@linux.intel.com \
    /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