All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <clarson@kergoth.com>
To: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Cc: mdf@kernel.org, Philip Balister <philip@opensdr.com>
Subject: Re: [PATCH] devtools: Add recipe for Chromium Embedded Controller utilities
Date: Wed, 28 Dec 2016 11:43:46 -0700	[thread overview]
Message-ID: <CABcZANm34+wJ7=ibqjNNhUpW3XjV2mwNAOy1Gh6bMhxU_Q=GQA@mail.gmail.com> (raw)
In-Reply-To: <1482949868-19842-1-git-send-email-moritz.fischer@ettus.com>

On Wed, Dec 28, 2016 at 11:31 AM, Moritz Fischer <moritz.fischer@ettus.com>
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>
>

Thanks for your contribution, they’re always appreciated. In the future,
try to keep in mind that the subject line needs a correct prefix for oe
commit message standards (prefix with recipe name, not recipes subdir
name), and the email subject should mention which layer you want it applied
to (though one can determine it based on context, best practice is to
include it). I’ll leave it to the layer maintainer to determine whether you
need to re-send or just keep it in mind for future patches.

Thanks again,
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics


  reply	other threads:[~2016-12-28 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 18:31 [PATCH] devtools: Add recipe for Chromium Embedded Controller utilities Moritz Fischer
2016-12-28 18:43 ` Christopher Larson [this message]
2016-12-28 21:43 ` Martin Jansa
2016-12-28 21:44   ` Martin Jansa
2016-12-28 23:25 ` 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='CABcZANm34+wJ7=ibqjNNhUpW3XjV2mwNAOy1Gh6bMhxU_Q=GQA@mail.gmail.com' \
    --to=clarson@kergoth.com \
    --cc=mdf@kernel.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=philip@opensdr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.