Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Moritz Fischer <moritz.fischer@ettus.com>
Cc: koen@dominion.thruhere.net, mdf@kernel.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v5] Chromium-utils: add recipe for Chromium Embedded Controller utilities
Date: Thu, 19 Jan 2017 12:44:29 +0100	[thread overview]
Message-ID: <20170119114429.GF3265@jama> (raw)
In-Reply-To: <1484175013-360-1-git-send-email-moritz.fischer@ettus.com>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Wed, Jan 11, 2017 at 02:50:13PM -0800, Moritz Fischer wrote:
> Add a recipe to build 'ectool' a utility to interact with the embedded
> controller on Google's chromebooks (and other platforms using it).
> 
> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> ---
> Changes from v1:
> 
> - Replaced DESCRIPTION with SUMMARY (Martin)
> - Use EXTRA_OEMAKE (Martin)
> - Removed FILESEXTRAPATHS (Martin)
> - Changed PV (Martin / Khem)
> - Removed FILES_PN (Khem)
> 
> Changes from v2:
> 
> - Changed PV (Martin)
> 
> Changes from v3:
> 
> - Patch now against meta-oe (Khem, Ross)
> - No longer need patch for HOST_LDFLAGS since merged upstream
> 
> Changes from v4:
> - Change commitmsg (Koen)
> - Install to ${sbindir} vs ${bindir} (Koen)

Fails to build because of missing dependencies, see:
http://errors.yoctoproject.org/Errors/Details/117457/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 22:50 [meta-oe][PATCH v5] Chromium-utils: add recipe for Chromium Embedded Controller utilities Moritz Fischer
2017-01-19 11:44 ` Martin Jansa [this message]

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=20170119114429.GF3265@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=mdf@kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=openembedded-devel@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