All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/3][dizzy] several backports for iot-devkit compatibility
Date: Mon,  8 Jun 2015 15:42:37 +0000	[thread overview]
Message-ID: <cover.1433777512.git.alejandro.hernandez@linux.intel.com> (raw)

I would like to include these backports from [master] on [dizzy] for compatibility with iot-devkit

The packages to be backported/upgraded are:

libftdi
lirc
p7zip


The following changes since commit 5b6f39ce325d490fc382d5d59c5b8b9d5fa38b38:

  gsoap: fold .inc and -native into one recipe (2015-04-29 19:24:09 +0200)


Alejandro Hernandez (3):
  libftdi: backport to dizzy for compatibility with iot-devkit
  lirc: backport to dizzy for compatibility with iot-devkit
  p7zip: backport to dizzy for compatibility with iot-devkit

 meta-oe/recipes-connectivity/lirc/lirc.inc         |   14 +
 .../recipes-connectivity/lirc/lirc/lirc.tmpfiles   |    1 +
 .../lirc/lirc/lirc_options.conf                    |   24 +
 meta-oe/recipes-connectivity/lirc/lirc/lircd.conf  |  315 +
 meta-oe/recipes-connectivity/lirc/lirc/lircd.init  |   40 +
 .../recipes-connectivity/lirc/lirc/lircd.service   |   20 +
 .../recipes-connectivity/lirc/lirc/lircexec.init   |   37 +
 meta-oe/recipes-connectivity/lirc/lirc_0.9.2.bb    |   69 +
 ...do_not_override_compiler_and_do_not_strip.patch |   31 +
 meta-oe/recipes-extended/p7zip/p7zip_9.20.1.bb     |   17 +
 .../libftdi/libftdi-0.19/libtool-m4.patch          | 7377 --------------------
 meta-oe/recipes-support/libftdi/libftdi_0.19.bb    |   31 -
 meta-oe/recipes-support/libftdi/libftdi_1.1.bb     |   29 +
 13 files changed, 597 insertions(+), 7408 deletions(-)
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc.inc
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lirc.tmpfiles
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lirc_options.conf
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lircd.conf
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lircd.init
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lircd.service
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc/lircexec.init
 create mode 100644 meta-oe/recipes-connectivity/lirc/lirc_0.9.2.bb
 create mode 100644 meta-oe/recipes-extended/p7zip/files/do_not_override_compiler_and_do_not_strip.patch
 create mode 100644 meta-oe/recipes-extended/p7zip/p7zip_9.20.1.bb
 delete mode 100644 meta-oe/recipes-support/libftdi/libftdi-0.19/libtool-m4.patch
 delete mode 100644 meta-oe/recipes-support/libftdi/libftdi_0.19.bb
 create mode 100644 meta-oe/recipes-support/libftdi/libftdi_1.1.bb

-- 
1.8.4.5



             reply	other threads:[~2015-06-08 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 15:42 Alejandro Hernandez [this message]
2015-06-08 15:42 ` [meta-oe][PATCH 1/3][dizzy] libftdi: backport to dizzy for compatibility with iot-devkit Alejandro Hernandez
2015-06-08 15:42 ` [meta-oe][PATCH 2/3][dizzy] lirc: " Alejandro Hernandez
2015-06-08 15:42 ` [meta-oe][PATCH 3/3][dizzy] p7zip: " Alejandro Hernandez
2015-06-14  6:05 ` [meta-oe][PATCH 0/3][dizzy] several backports for iot-devkit compatibility akuster808

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.1433777512.git.alejandro.hernandez@linux.intel.com \
    --to=alejandro.hernandez@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 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.