Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for UEFI + Secure Boot + qemu (rev4)
Date: Fri, 20 Jan 2017 15:07:04 +0100	[thread overview]
Message-ID: <1484921224.23233.123.camel@intel.com> (raw)
In-Reply-To: <20170120135343.23276.63313@do.openembedded.org>

On Fri, 2017-01-20 at 13:53 +0000, Patchwork wrote:
> * Issue             A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence] 
>   Suggested fix    Sign off the added patch file (meta/recipes-extended/acpica/acpitests/aapits-linux.patch)
> 
> * Issue             Added patch file is missing Upstream-Status in the header [test_upstream_status_presence] 
>   Suggested fix    Add Upstream-Status: <status> to the header of meta/recipes-extended/acpica/acpitests/aapits-linux.patch (possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)

This is intentional: I'm not the original author and didn't want to mess
too much with the recipe. Should I add Upstream-Status in a separate
commit?

> * 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 ce5c7075d5)

Argh, apparently I only meant to rebase and then didn't. Will resolve
this and send V4.

But it's good that patchtest is finding this promptly, kudos!

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-01-20 14:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 13:37 [PATCH v3 00/12] UEFI + Secure Boot + qemu Patrick Ohly
2017-01-20 13:37 ` [PATCH v3 01/12] acpica: move from meta-oe to OE-core Patrick Ohly
2017-01-20 13:37 ` [PATCH v3 02/12] ovmf: move from meta-luv " Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 03/12] ovmf: explicitly depend on nasm-native Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 04/12] ovmf: deploy firmware in image directory Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 05/12] ovmf_git.bb: enable parallel compilation Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 06/12] ovmf_git.bb: enable Secure Boot Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 07/12] runqemu: also accept -image suffix for rootfs parameter Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 08/12] runqemu: fix undefined variable reference in check_arg_path() Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 09/12] runqemu: support UEFI with OVMF firmware Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 10/12] ovmf: build image which enrolls standard keys Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 11/12] ovmf: remove BGRT patch Patrick Ohly
2017-01-20 13:38 ` [PATCH v3 12/12] acpica: work around flex 2.6.2 code generation issue Patrick Ohly
2017-01-20 13:53 ` ✗ patchtest: failure for UEFI + Secure Boot + qemu (rev4) Patchwork
2017-01-20 14:07   ` Patrick Ohly [this message]
2017-01-20 14:08     ` Burton, Ross

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=1484921224.23233.123.camel@intel.com \
    --to=patrick.ohly@intel.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