From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Moritz Fischer <moritz.fischer@ettus.com>,
openembedded-core@lists.openembedded.org
Cc: koen@dominion.thruhere.net, mdf@kernel.org
Subject: Re: [meta-oe][PATCH v3] devtools: Add recipe for Chromium Embedded Controller utilities
Date: Wed, 4 Jan 2017 12:36:28 -0600 [thread overview]
Message-ID: <740a7531-d635-8191-d901-ffaa0deffae4@linux.intel.com> (raw)
In-Reply-To: <1483512355-27961-1-git-send-email-moritz.fischer@ettus.com>
> +}
> diff --git a/meta/recipes-devtools/chromium-utils/files/0001-build-Add-HOST_LDFLAGS.patch b/meta/recipes-devtools/chromium-utils/files/0001-build-Add-HOST_LDFLAGS.patch
> new file mode 100644
> index 0000000..46e8cad
> --- /dev/null
> +++ b/meta/recipes-devtools/chromium-utils/files/0001-build-Add-HOST_LDFLAGS.patch
> @@ -0,0 +1,26 @@
> +From 56ffeeffea735a6a8f69fc111278ebabe3c7e2d8 Mon Sep 17 00:00:00 2001
> +From: Moritz Fischer <moritz.fischer@ettus.com>
> +Date: Tue, 27 Dec 2016 22:24:07 -0800
> +Subject: [PATCH] build Add HOST_LDFLAGS
> +
what is the Upstream Status of this patch? At least for oe-core, you
need to provide it. More info at
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> +Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> +---
> + Makefile.rules | 2 +-
>
next prev parent reply other threads:[~2017-01-04 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 6:45 [meta-oe][PATCH v3] devtools: Add recipe for Chromium Embedded Controller utilities Moritz Fischer
2017-01-04 18:36 ` Leonardo Sandoval [this message]
2017-01-04 20:25 ` Moritz Fischer
2017-01-04 20:39 ` Burton, Ross
2017-01-05 1:29 ` Khem Raj
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=740a7531-d635-8191-d901-ffaa0deffae4@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=mdf@kernel.org \
--cc=moritz.fischer@ettus.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