Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/2] Add mraa/upm recipes from meta-refkit-core
Date: Wed, 27 Sep 2017 00:08:49 +1300	[thread overview]
Message-ID: <cover.1506424098.git.paul.eggleton@linux.intel.com> (raw)

Move in recipes from meta-refkit-core for the mraa I/O library and upm
sensor library.


The following changes since commit f841648657069051dffa1012a42eb1524b894d50:

  openwsman: Fix build with musl (2017-09-22 22:56:13 +0000)

are available in the git repository at:

  git://git.openembedded.org/meta-openembedded-contrib paule/mraa
  http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=paule/mraa

Paul Eggleton (2):
  mraa: move recipe from meta-refkit-core
  upm: add recipe from meta-refkit-core

 meta-oe/recipes-extended/mraa/mraa_git.bb          | 48 +++++++++++++++++++
 ...15-fixed-case-logic-in-getThresh-function.patch | 54 ++++++++++++++++++++++
 meta-oe/recipes-extended/upm/upm_git.bb            | 42 +++++++++++++++++
 3 files changed, 144 insertions(+)
 create mode 100644 meta-oe/recipes-extended/mraa/mraa_git.bb
 create mode 100644 meta-oe/recipes-extended/upm/files/ads1x15-fixed-case-logic-in-getThresh-function.patch
 create mode 100644 meta-oe/recipes-extended/upm/upm_git.bb

-- 
2.9.5



             reply	other threads:[~2017-09-26 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 11:08 Paul Eggleton [this message]
2017-09-26 11:08 ` [meta-oe][PATCH 1/2] mraa: move recipe from meta-refkit-core Paul Eggleton
2017-10-02 18:21   ` Khem Raj
2017-10-02 19:40     ` Paul Eggleton
2017-09-26 11:08 ` [meta-oe][PATCH 2/2] upm: add " Paul Eggleton

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=cover.1506424098.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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