Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Wold, Saul" <saul.wold@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH][morty] gnu-efi: Fix missing space in _append line
Date: Mon, 20 Nov 2017 19:01:23 +0000	[thread overview]
Message-ID: <1511204481.933.45.camel@intel.com> (raw)
In-Reply-To: <20171120190028.24015-1-sgw@linux.intel.com>


Wrong list, this is for meta-intel, sorry.

Sau!

On Mon, 2017-11-20 at 11:00 -0800, Saul Wold wrote:
> [YOCTO #12366]
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> 
> This is only in Morty, so no master then backport option
> 
>  common/recipes-bsp/gnu-efi/gnu-efi_%.bbappend | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/common/recipes-bsp/gnu-efi/gnu-efi_%.bbappend
> b/common/recipes-bsp/gnu-efi/gnu-efi_%.bbappend
> index 1e9cfda..da08432 100644
> --- a/common/recipes-bsp/gnu-efi/gnu-efi_%.bbappend
> +++ b/common/recipes-bsp/gnu-efi/gnu-efi_%.bbappend
> @@ -1,3 +1,3 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/gnu-efi:"
> -SRC_URI_append_intel-x86-common = "file://0001-Add-GUID-for-SMBIOS-
> 3-entry-point-structure.patch"
> +SRC_URI_append_intel-x86-common = " file://0001-Add-GUID-for-SMBIOS-
> 3-entry-point-structure.patch"
>  PACKAGE_ARCH_intel-x86-common = "${INTEL_COMMON_PACKAGE_ARCH}"
> -- 
> 2.13.5
> 

  reply	other threads:[~2017-11-20 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 19:00 [PATCH][morty] gnu-efi: Fix missing space in _append line Saul Wold
2017-11-20 19:01 ` Wold, Saul [this message]
2017-11-20 19:32 ` ✗ 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=1511204481.933.45.camel@intel.com \
    --to=saul.wold@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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